Wireless lighting control system

ABSTRACT

A lighting device includes a DC/DC power converter, a controller/processor electrically connected to the DC/DC power converter, a light emitting diode (LED) current control circuit communicably coupled to the controller/processor and electrically connected to the DC/DC power converter, and two or more LEDs comprising at least a first color LED and a second color LED electrically connected to the LED current control circuit. The LED current control circuit provides an on/off signal having a cycle time to each LED in response to one or more control signals received from the controller/processor such that the two or more LEDs produce a blended light having a specified color based on how long each LED is turned ON and/or OFF during the cycle time.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and is a continuation application ofU.S. patent application Ser. No. 13/417,322, filed Mar. 11, 2012, andentitled “Wireless Lighting Control System”, which is a non-provisionalpatent application of U.S. Provisional Application Ser. No. 61/464,917,filed Mar. 11, 2011, and entitled “Specialty Lighting and ControlTherefor.” In addition, this application claims priority to PCT PatentApplication Serial Number PCT/US2012/037369, filed May 10, 2012, andentitled “Wireless Lighting Control System.” The foregoing applicationsare hereby incorporated by reference in their entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to the field of lighting and,more particularly, to a specialty lighting device and control processfor individual or simultaneous adjustment, automation, and programmingof an individual or network of such lighting devices through a wirelessinterface.

2. Description of Related Art

In response to government mandates, new lighting technologies, such aslight emitting diodes (LEDs) or compact fluorescent lamps (CFLs), areentering the market at a rapid pace. However, these bulbs havelimitations that make them unattractive to some users. CFLs have dimminglimitations, take a few minutes to warm-up, and have problems with theircolor output. Additionally, CFLs contain mercury, a toxic and regulatedsubstance, which creates issues with disposal. LEDs are currently veryexpensive in comparison and the high cost has dissuaded many consumersfrom their purchase.

Additionally, current lighting control and automation solutions arelimited in their use in rental or temporary situations where the systemshigh price, required installation, and expertise in set-up are aproblem. Further, as mobile computing systems continue to evolve, manypeople have shown a preference towards using their mobile device as aconverged platform to control and execute multiple other tasks. Althougha multitude of types of light types and luminaires have been created tohelp create a mood or environment, most if not all of these solutionsonly exist in a single state and are limited by the network power line.This has driven the complexity in bulb wattage, fixtures, wall-switches,shades, and other attempts at creating the ability to augment theatmosphere created by a light. If you want to dim one bulb, currentsolutions generally only allow for a wall-switch dimmer. The ability toaddress and adjust a single light individually or network of lightssimultaneously is currently not possible without extensive installation.

SUMMARY OF THE INVENTION

The present invention provides an easily installed and transferablelighting and home automation solution because special or customizedinstallation is not required. The present invention presents a solutionto controlling and programming lighting devices, such that the color andbrightness of any individual light or a group of lights can be manuallyor automatically controlled using a wireless interface. A user has theflexibility to personalize the color, atmosphere, and mood of a room tobetter fit ones preference, time of day, or occasion at hand.

Additionally, since the present invention requires no installation, thesolution is fully portable and can be removed and reused in otherlocations throughout the long life of the device. Essentially, thepresent invention is an automation and custom lighting solution that cantravel with you.

Automation and dimming of the lighting devices save more energy than isconsumed by the additional components of the lighting device. Moreover,using on/off signals having specified cycle times to produce a blendedlight reduce the current requirements of the lighting device. Lastly,holistically speaking the iLumi solution itself will help to drive theadoption of LED bulbs, providing an LED solution whose value outweighsits price.

More specifically, the present invention provides a lighting device thatincludes a DC/DC power converter, a controller/processor electricallyconnected to the DC/DC power converter, a light emitting diode (LED)current control circuit communicably coupled to the controller/processorand electrically connected to the DC/DC power converter, and two or moreLEDs comprising at least a first color LED and a second color LEDelectrically connected to the LED current control circuit. The LEDcurrent control circuit provides an on/off signal having a cycle time toeach LED in response to one or more control signals received from thecontroller/processor such that the two or more LEDs produce a blendedlight having a specified color based on how long each LED is turned ONand/or OFF during the cycle time.

Moreover, the present invention provides a lighting device that includesa flexible strip, an electrical connector affixed to the flexible stripand two or more LEDs affixed to the flexible strip and electricallyconnected to the electrical connector. In addition, a DC/DC powerconverter, a controller/processor and a LED current control circuit areremotely located with respect to the flexible strip and electricallyconnected to the electrical connector via a wire, a cable or aconnecting strip. The LED current control circuit provides an on/offsignal having a cycle time to each LED in response to one or morecontrol signals received from the controller/processor such that the twoor more LEDs produce a blended light having a specified color based onhow long each LED is turned ON and/or OFF during the cycle time.

Furthermore, the present invention provides a lighting device thatincludes a housing, a DC/DC power converter, a controller/processorelectrically connected to the DC/DC power converter, a light emittingdiode (LED) current control circuit communicably coupled to thecontroller/processor and electrically connected to the DC/DC powerconverter, and two or more LEDs comprising at least a first color LEDand a second color LED electrically connected to the LED current controlcircuit. The DC/DC power converter, the controller/processor and the LEDcurrent control circuit are disposed within the housing, and the two ormore LEDs are proximate to or within an aperture of the housing. The LEDcurrent control circuit provides an on/off signal having a cycle time toeach LED in response to one or more control signals received from thecontroller/processor such that the two or more LEDs produce a blendedlight having a specified color based on how long each LED is turned ONand/or OFF during the cycle time.

In addition, the present invention provides a lighting system thatincludes two or more lighting devices. Each lighting device includes aDC/DC power converter, a controller/processor electrically connected tothe DC/DC power converter, a light emitting diode (LED) current controlcircuit communicably coupled to the controller/processor andelectrically connected to the DC/DC power converter, and two or moreLEDs comprising at least a first color LED and a second color LEDelectrically connected to the LED current control circuit. The LEDcurrent control circuit provides an on/off signal having a cycle time toeach LED in response to one or more control signals received from thecontroller/processor such that the two or more LEDs produce a blendedlight having a specified color based on how long each LED is turned ONand/or OFF during the cycle time. The controller/processors of the twoor more lighting devices communicate with one another using the wirelesstransceivers and antennas of the two or more lighting devices.

The present invention also provides method for controlling one or morelighting devices by providing the one or more lighting devices, whereineach lighting device includes a DC/DC power converter, acontroller/processor electrically connected to the DC/DC powerconverter, a light emitting diode (LED) current control circuitcommunicably coupled to the controller/processor and electricallyconnected to the DC/DC power converter, and two or more LEDs comprisingat least a first color LED and a second color LED electrically connectedto the LED current control circuit. One or more control signals are sentfrom the controller/processor to the LED current control circuitcorresponding to a blended light having a specified color. An on/offsignal having a cycle time is sent from the LED current control circuitto each LED in response to the one or more control signals such that thetwo or more LEDs produce the blended light having the specified colorbased on how long each LED is turned ON and/or OFF during the cycletime.

These and other objects, advantages and features of this invention willbe apparent from the following description taken with reference to theaccompanying drawing, wherein is shown a preferred embodiment of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and further advantages of the invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings, in which:

FIG. 1 is a block diagram of a lighting device in accordance with oneembodiment of the present invention;

FIG. 2 is a circuit diagram of a single LED arm with single LED inaccordance with one embodiment of the present invention;

FIG. 3 is a circuit diagram of a solely LED Drivers scheme in accordancewith one embodiment of the present invention;

FIG. 4 is a timing diagram for the solely LED drivers scheme of FIG. 3;

FIG. 5 is a circuit diagram of switches and LED driver scheme inaccordance with one embodiment of the present invention;

FIG. 6 is a timing diagram for the switches and LED driver scheme ofFIG. 5;

FIG. 7 is a circuit diagram of a multiplexer and a LED driver scheme inaccordance with one embodiment of the present invention;

FIG. 8 is a circuit diagram of current limiting circuit scheme inaccordance with one embodiment of the present invention;

FIG. 9 is a diagram of a Smart strip light mechanical model inaccordance with one embodiment of the present invention;

FIG. 10 is a block diagram of a Smart strip light in accordance with oneembodiment of the present invention;

FIG. 11 is a circuit diagram of LEDs groups on LEDs strip in accordancewith one embodiment of the present invention;

FIGS. 12A-1 and 12A-2 are block diagrams of a front view and a rearview, respectively of a LEDs strip in accordance with one embodiment ofthe present invention;

FIGS. 12B-1 and 12B-2 are block diagrams of a front view and a rearview, respectively, of an extendible LEDs strip in accordance with oneembodiment of the present invention;

FIG. 13 is a block diagram of the Smart strip light mechanical andelectrical connections in accordance with one embodiment of the presentinvention;

FIG. 14 is a block diagram of an extendible LEDs strip in accordancewith one embodiment of the present invention;

FIG. 15 is a block diagram of a LEDs strip extension through parallelconnection in accordance with one embodiment of the present invention;

FIG. 16 is a block diagram of a LEDs strips direct connection inaccordance with one embodiment of the present invention;

FIG. 17 is a block diagram of a LEDs strip connection through wire inaccordance with one embodiment of the present invention;

FIG. 18 is a perspective view of an Intelligent Illuminating Bulb inaccordance with one embodiment of the present invention;

FIG. 19 is an exploded perspective view of an Intelligent IlluminatingBulb in accordance with one embodiment of the present invention;

FIG. 20 is a diagram of a LEDs board in accordance with one embodimentof the present invention;

FIG. 21 is a flow chart of a status request/update process for awireless device or auxiliary device to Intelligent Illuminating Devicein accordance with one embodiment of the present invention;

FIG. 22 is a flow chart of a status update process for IntelligentIlluminating Device to Intelligent Illuminating Device in accordancewith one embodiment of the present invention;

FIG. 23 is a flow chart of a communication process from a device toIntelligent Illuminating Device in accordance with one embodiment of thepresent invention;

FIG. 24 is a flow chart of a communication process from a device tomultiple Intelligent Illuminating Devices in accordance with oneembodiment of the present invention;

FIG. 25 is a block diagram of accessing an Intelligent IlluminatingDevice network through various devices in accordance with one embodimentof the present invention;

FIG. 26 is a flow chart of a wireless device update date/time process inIntelligent Illuminating Device in accordance with one embodiment of thepresent invention;

FIG. 27 is a flow chart of an Intelligent Illuminating Device updatedate/time in Intelligent Illuminating Device in accordance with oneembodiment of the present invention;

FIG. 28 is a flow chart of basic control areas in accordance with oneembodiment of the present invention;

FIG. 29 is a flow chart of a programming process in accordance with oneembodiment of the present invention;

FIG. 30 is a flow chart of a process for creating a scene in accordancewith one embodiment of the present invention;

FIG. 31 is a flow chart of a process for executing a scene command inaccordance with one embodiment of the present invention;

FIG. 32 is a flow chart of a process for creating a new group or addingto a new group in accordance with one embodiment of the presentinvention;

FIG. 33 is a flow chart of a process for sending a group command inaccordance with one embodiment of the present invention;

FIG. 34 is a flow chart of a process for creating or adjusting a lightdefault in accordance with one embodiment of the present invention;

FIG. 35 is a flow chart of a process for creating or adjust a groupdefault in accordance with one embodiment of the present invention;

FIG. 36 is a flow chart of a power restoration process in accordancewith one embodiment of the present invention;

FIG. 37 is a flow chart of a process for executing a default commandthrough an on/off toggle in accordance with one embodiment of thepresent invention;

FIGS. 38A-38F are diagrams of various screens on device application inaccordance with one embodiment of the present invention;

FIG. 39 is a flow chart of a quick set-up process for connected lightsin accordance with one embodiment of the present invention;

FIG. 40 is a flow chart of a quick group process through powerrestoration in accordance with one embodiment of the present invention;

FIG. 41 is a flow chart of a profile authentication process inaccordance with one embodiment of the present invention;

FIG. 42 is a flow chart of a process for saving settings under a profilein accordance with one embodiment of the present invention;

FIG. 43 is a block diagram of a device to device profile sharing processin accordance with one embodiment of the present invention;

FIG. 44 is a flow chart of a process for adding an authenticated profiledirectly through the Intelligent Illuminating Device in accordance withone embodiment of the present invention;

FIG. 45 is a flow chart of a hard reset process in accordance with oneembodiment of the present invention;

FIG. 46 is a flow chart of a soft reset through application inaccordance with one embodiment of the present invention;

FIG. 47 is a flow chart of a process for adding a new IntelligentIlluminating Device into an existing Intelligent Illuminating Devicenetwork in accordance with one embodiment of the present invention;

FIG. 48 is a block diagram of another embodiment of II Device systemwith a wireless energy receiver and transmitter in accordance with oneembodiment of the present invention;

FIG. 49 is a block diagram of a color coding identification process inaccordance with one embodiment of the present invention;

FIG. 50 is a block diagram of sorting based on signal strength inaccordance with one embodiment of the present invention;

FIG. 51 is a block diagram of sorting based on status in accordance withone embodiment of the present invention;

FIG. 52 is a block diagram of sorting based on available IntelligentIlluminating Devices in accordance with one embodiment of the presentinvention;

FIG. 53 is a flow chart of an automation programming process inaccordance with one embodiment of the present invention; and

FIG. 54 is a flow chart of a music sync process in accordance with oneembodiment of the present invention; and

FIG. 55 is a block diagram of showing a potential placement of thephotosensor and reset switch on the light mixing cover/diffuser inaccordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

While the making and using of various embodiments of the presentinvention are discussed in detail below, it should be appreciated thatthe present invention provides many applicable inventive concepts thatcan be embodied in a wide variety of specific contexts. The specificembodiments discussed herein are merely illustrative of specific ways tomake and use the invention and do not delimit the scope of theinvention.

The present invention provides an easily installed and transferablelighting and home automation solution because special or customizedinstallation is not required. The present invention presents a solutionto controlling, programming, and automating lighting devices, such thatthe color and brightness of any individual light or a group of lightscan be manually or automatically controlled using a wireless interface.A user has the flexibility to personalize the color, atmosphere, andmood of a room to better fit ones preference, time of day, or occasionat hand. Additionally, since the present invention requires noinstallation, the solution is fully portable and can be removed andreused in other locations throughout the long life of the lightingdevice. Automation and dimming of the lighting devices save more energythan is consumed by the additional components of the lighting device.Moreover, using on/off signals having specified cycle times to produce ablended light reduce the current requirements of the lighting device.

The present invention, a wireless lighting control system, consists ofmethods, apparatuses, and associated software (device application) forcontrolling, programming, and automating one and/or multiple‘Intelligent Illuminating Devices’ (II Device) utilizing a wirelesscommunication protocol executed between one or many wireless devices andone or many II Devices (II Device network). The methods and apparatusespresented here would allow one to adjust and control a single or networkof II Devices with high flexibility, user control, and intuitive userinteraction, with minimal installation or complexity.

For the purposes of discussing this invention the following terms willbe used to describe the primary aspects of the invention. An II Deviceis a single wirelessly enabled lighting apparatus. A wireless device isa computing device such as a smartphone, computer, tablet, smartTV,remote, etc. A device application is a user facing software applicationrun on the wireless device. A mesh network is a wireless communicationprotocol used to connect one or many II Devices and/or one or manywireless devices.

The light part is a combination of a light generator, a light detector,a communicator, a power source, and a computer processor. In oneembodiment these components are contained within one form factor similarto a standard light bulb. In other embodiments these elements will beseparate from the other elements. For example, the light generator willbe separate from the remaining means. In other embodiments, all meansare not required. For example an embodiment may consist solely of thelighting means, communications means, and computer processor. In otherembodiments some means might be of an outside source. For example, anoutside light sensing means the might be disparately connected to theremaining means.

An II Device in the context of this invention is a lighting apparatuscontaining additional electronic circuits and components. In oneembodiment, the II Device will produce some measure or effect ofluminosity dependent on commands sent wirelessly through a wirelessdevice and associated device application. The II Device can receivewireless communications, take immediate action (in terms of a lightingoutput) based on the wireless communication, execute a sequence ofactions, and store one or more commands to be executed at a specifiedtime in the future or upon a specified condition being met. In addition,one embodiment of the II Device can intelligently relay/transmitwireless communication commands received from a device application (orII Device) to other II Devices within proximity. Similarly, oneembodiment of the II Device would confirm receipt of the command througha wireless communication back to the wireless device and deviceapplication, possibly relaying the confirmation back through other IIDevices. The communication means for to execute these processes can beseen in the mesh network section.

Now referring to FIG. 1, a block diagram of a lighting device inaccordance with one embodiment of the present invention is shown. Thelighting device (II Device) 140 might take numerous forms or embodimentsin design, but certain components are common to the various designswhile others will be used as is necessary for a specific embodiment.These components may or may not be part of II Device 140 and might bearranged in different fashion and with slight alteration to createdifferent intelligent illuminating embodiments. For example, the IIDevice 140 includes a DC/DC power converter 104, a controller/processor106 electrically connected to the DC/DC power converter 104, a lightemitting diode (LED) current control circuit 120 communicably coupled tothe controller/processor 106 and electrically connected to the DC/DCpower converter 104, and two or more LEDs 122 electrically connected tothe LED current control circuit 120. The LED current control circuit 120can be a PWM driver, switching or multiplexer circuit, or light emittingdiodes (LEDs) driver(s) circuit. The two or more LEDs 122 will includeat least a first color LED 122 a and a second color LED 122 b. Moreover,at least one of the LEDs 122 may include a series of LEDs, a group ofLEDs, an array of LEDs, two or more series-connected LEDs, two or moreparallel-connected LEDs or a combination thereof. Typically, the firstcolor LED 122 a and the second color LED 122 b will be selected from ared LED, a green LED, a blue LED, a red LED, a white LED and a tri-colorLED.

As will be explained in more detail below, a method for controlling oneor more lighting devices 140 includes the steps of providing the one ormore lighting devices 140, sending one or more control signals from thecontroller/processor 106 to the LED current control circuit 120corresponding to a blended light having a specified color, and sendingan on/off signal having a cycle time from the LED current controlcircuit 120 to each LED 122 in response to the one or more controlsignals such that the two or more LEDs 122 produce the blended lighthaving the specified color based on how long each LED 122 is turned ONand/or OFF during the cycle time. The LED current control circuit 120provides an on/off signal having a cycle time to each LED 122 inresponse to one or more control signals received from thecontroller/processor 106 such that the two or more LEDs 122 produce ablended light having a specified color based on how long each LED isturned ON and/or OFF during the cycle time. These on/off signals withspecified cycle times to produce a blended light can be used to reducethe current requirements of the II Device 140.

Other embodiments will include additional components. For example, theadditional components may include: a power supply connector/fastener100; an AC/DC power converter 102 electrically connected to the powersupply connector/fastener 100 and the DC/DC power converter 104; a realtime clock (RTC) circuit 110 communicably coupled to thecontroller/processor 106; a memory 108 communicably coupled to thecontroller/processor 106; a wireless transceiver circuit 112communicably coupled to the controller/processor 106; an antenna 114communicably coupled to the wireless transceiver circuit 112; a hardreset circuit 116 communicably coupled to the controller/processor 106;an ambient light sensor circuit 118 communicably coupled to thecontroller/processor 106; a heat sink 124; a reflector 126 disposedbehind or around the two or more LEDs 122; and/or a diffuser or lens 128disposed above the two or more LEDs 122.

The components of the II Device 140 can be modularized to provide easyenhancement, customization, modification and repair of the II Device140. For example, a main circuit board 134 may include the DC/DC powerconverter 104, the controller/processor 106, the LED current controlcircuit 120, the memory 108, the real time clock circuit 110, and thewireless transceiver circuit 112 and antenna 114. A sensor board 130 mayinclude the hard reset circuit 116 and the ambient light sensor circuit118. A LED board 136 may include the two or more LEDs 122 and additionalLED related circuitry (e.g., LED arms).

The connector 100 performs at least one of two functions. One, it canphysically connect the II Device 140 to a surface and two, it canprovide access to a power source. The connector 100 could fasten to astandard surface, light socket, or electrical socket, or combination ofthe like. Similarly, the connector 100 could provide a connection to apower source as an Edison base (multiple sizes), Plug in, Bi-pin, orBattery connected connection (including water activated battery), etc.The connector 100 would conduct the electrical current through to the ACto DC converter 102. In some embodiments, such as the IntelligentIlluminating Strip (II Strip or Smartstrip) 900 (FIG. 9), the fastenerand power connection means of the connector 100 might be separated. Forexample, an electrical plug is connected via a wire to the rest of theSmartstrip and the Smartstrip is fastened in some other manner (such asscrews or adhesive) to a surface. In other embodiments, such as theIntelligent Illuminating Bulb (II Bulb) 1800 (FIG. 18), the connector100 would be an Edison base or bi-pin for which when the connector isinserted into the appropriate light socket, the connector 100 wouldprovide appropriate contact to extend the AC or DC power source orsupply into the body of the II Bulb 1800. In addition, the connector 100might provide some structural stability in fastening the II Device 140to a surface.

The AC to DC converter 102 receives power from the connector 100 andoutputs the appropriate DC power to the DC/DC converter 104, the LEDcurrent controlling 120 circuit, and LED circuit 122. The exact powerinput might vary depending on country specific standards or powersources, but as a universal converter, the power output will always beDC voltage such as 12 VDC or 18 VDC or 24 VDC. Examples of power inputsinclude AC power 60 V-290 V/45-65 Hz or (Examples: 230 VAC/50 Hz(European/Indian Standard), 110 VAC/60 Hz (US Standard), or a range ofDC power from 12 VDC to 1000 VDC. The AC to DC converter 102 might behoused within the connector 100 or separate from the connector 100,depending on the specific II Device embodiment.

The DC/DC converter(s) 104 receives a power input from the AC/DCconverter 102, it then converts that power to DC power(s) required fordriving the internal components/modules of the II Device 140. Thesecomponents include the controller/processor 106, memory 108, the realtime clock (RTC) circuit 110, the wireless transceiver circuit 112,antenna 114, and possibly components within the LED current controlcircuit 120. It might also supply power to other components, such as thehard reset circuit 116, the ambient light sensor circuit 118, and otherpotential added circuits. There might be multiple converters dependenton the output DC voltages required by different component requirements.Similarly, the power output would very dependent on the exact componentrequirements, for example the output might be 5 VDC, 3.3 VDC, or 1.3VDC.

The controller/processor 106 processes signals received from the memory108, the real time clock (RTC) circuit 110, and the wireless transceivercircuit 112. It might also process signals from other components, suchas the hard reset circuit 116, the ambient light sensor circuit 118, andother potential added circuits. It also takes action and sends commandsto the memory 108, the real time clock (RTC) circuit 110, and thewireless transceiver circuit 112. It might also take action and sendsignals to other components, such as the ambient light sensor circuit118 and other potential added circuits. In one embodiment, the computerprocessor includes a real time clock, processor 106, and memory chip.

The processor processes the signals received by the various othercomponents of the embodiment, computes necessary actions, and sendssignals back out to various other components of the embodiment. Thecomputer processor will vary in terms of power, speed, and size indifferent embodiments. Additionally, the computer processor is notlimited to the contents listed above and may include other components.

The memory 108 stores data from factory defined settings and from userdefined settings. The controller/processor 106 will read/write data inmemory 108. Data might include factory-defined settings, such ascommunication protocols, identification and security protocols, andother data. Data might also include user-defined settings, such as userprofiles, default commands, programs, and other data. The memory 108could be inside the processor 106 and/or external to the processor 106as a different integrated circuit or chip(s). The controller/processor106 and memory 108 circuits might take a number of different technicalspecifications. In one embodiment, the computer processor includes areal time clock, processor, and memory chip. The memory 108 receivesinformation from the processor 106 and stores the commands for retrievalby the processor 106.

The real time clock circuit 110 includes a battery and a date and timeclock based RTC. The controller/processor 106 will set the date and timedata in the RTC 110 and also read the date and time data from the RTC110. The RTC 110 could be internal to the controller/processor 106 or itcould be an external circuit with respect to the controller/processor106. The RTC 110 will run on the DC/DC power unless no power isprovided, in which case it will run on the battery included within thereal time clock circuit 106. The battery could be a rechargeablebattery, in which case the DC/DC power when supplied would also chargethe rechargeable battery through recharging circuitry. The battery couldalso be a non-chargeable battery. In one embodiment, the computerprocessor includes a real time clock, processor, and memory chip. Thereal-time clock is battery powered and could be set for any time anddate.

The wireless transceiver circuit 112 allows the II Device 140 tocommunicate with other wireless devices and/or other II Devices. Thewireless transceiver circuit 112 includes a transmitter and receivercircuit based on established wireless protocols. These protocols coulddiffer based on different II Device embodiments and changing wirelesscommunication standards. Example wireless protocols include but are notlimited to Bluetooth, ZigBee, Wi-Fi, and their related variants. Thewireless transceiver circuit 112 will be connected to thecontroller/processor 106 and the antenna 114. In one embodiment, thecommunicator is composed of a transmitter and receiver circuit based onBluetooth protocols. In other embodiments, the communications meansmight utilize other protocols including but not limited to ZigBee, WiFi,infrared, WiMax, LTE, ZWave, or other protocols not listed. In otherembodiments the communications means might include other component partsor circuitry.

The antenna 114 captures wireless communication signals and passes themto the wireless transceiver circuit 112 to decode those signals. Theantenna 114 could take multiple forms depending on the protocol andsignal frequency required. The physical location of the antenna 114and/or wireless transceiver circuit 112 could be placed in multiplephysical locations related to the II Device 140. For example, it mightbe placed outside of the II Device 140 or inside the II Device 140.Placing it outside, might increase the range of wireless communicationfor the II Device 140, especially when installed in locations with poorreception. Alternatively, the antenna might be built into the physicalstructure of the II Device 140 or be part of the main board 134 insidethe II Device 140.

LEDs 122 refer to a combination of LEDs or LED arms that are illuminateddepending on current passed through from the LED current control circuit120. The combination of LED arms or LEDs could be of various types andvarious colors dependent on the II Device embodiment. For example, theLEDs might vary in color such as red, green, blue, and/or white LEDs.The LEDs might also vary in their maximum output luminosity. Thecombination of illuminations of these LEDs could produce various levelsof brightness and/or color.

The LED current control circuit 120 executes commands from thecontroller/processor 106 to control the current passed through the LEDs122. The LED current control circuit 120 might take different formsdependent on the II Device embodiment as per the following schemes:solely LED drivers scheme (FIG. 3), switches and LED driver scheme (FIG.5), multiplexer and LED driver scheme (FIG. 7), and current limitingcircuit scheme (FIG. 8). In general, the controller/processor 106 sendscommands to LED drivers (208 or 318, 320, 322, 324, or 508), switches ormultiplexer (500, 502, 504, 506 or 702), which in turn controls thelight output by controlling the average current passed through the LEDs122. The average current would affect the overall luminosity of the IIDevice 140, such as that at lower average currents passed through theLED driver then the II Device would be dimmer.

For embodiments where multiple LED arms (302, 304, 306, and 308) arepresent, unique to the presented schemes is a method to maximize thepotential current passed through and subsequent luminosity of each LEDarm with limited available current from the AC/DC converter 102. This isdone by controlling the current passed through by the LED driver (208 or318, 320, 322, 324, or 508) so that only one LED driver (208 or 318 or320 or 322 or 324 or 508) can pass through current at a time. Thisallows each on/off signal to provide a maximum current supplied by theDC/DC power converter to the LED 122. By varying and alternating veryshort lengths of time that current is passed through different LED arms(302, 304, 306, 308) using LED current control circuit 120, the schemesalso allow the multiple LED arms (302, 304, 306, 308) to produce anoverall blended light that is capable of various colors, saturation, andbrightness. These schemes allow the II Device 140 to provide the highestlevel of individual luminosity emitted related to one of the LED arms(302, 304, 306, 308), such as white, red, blue, or green, while alsoallowing for all combinations of color, brightness, and saturation to beachievable.

In other words, the specified color is produced by turning ON the firstcolor LED 122 a for a first portion of the cycle time and turning ON thesecond color LED 122 b for a second portion of the cycle time. The twoor more LEDs 122 are not turned ON at the same time. The cycle time ispreferably short enough such that a user will not notice any flicker,which is usually around 85 Hz (about 12 ms), unless flicker is desired.The on/off signal for the first LED 122 a includes two or more pulsesduring a portion of the cycle time that the first LED 122 a is turnedON. Likewise, the on/off signal for the second LED 122 b includes two ormore pulses during a portion of the cycle time that the second LED 122 bis turned ON. The on/off signals can be adjusted to provide a specifiedcolor, saturation and brightness or intensity. The specified brightnessor intensity can be determined by a duty cycle of the on/off signals.

In one embodiment, the light generator is composed of LEDs, LED Drivers,and a light enhancement cover. The LEDs are Light Emitting Diodes ofvarious types and colors. The LED Drivers is the circuitry that drivesthe LEDs. It takes the commands from the processor for turning requiredLEDs at required brightness or intensity.

One potential scheme for the LED current control circuit 120 is the‘solely LED drivers scheme’ (FIG. 3). In this scheme thecontroller/processor 106 would send one or multiple Pulse WidthModulation (PWM) Signals to one or many LED drivers (318, 320, 322, 324)which would control the current flowing through an associated LED arm(302, 304, 306, 308 respectively). There would be the same number of PWMsignals (326/400, 328/402, 330/404, 332/406) sent as there would be LEDdrivers (318, 320, 322, 324) and LED arms (302, 304, 306, 308). Thetotal number of LEDs strings (arms) and LED drivers depend upon theapplication. LED driver circuit is designed for a particular currentlevel to pass through it, so the LED driver circuit (318, 320, 322, 324)will regulate the flow of current through the respective LED arm (302,304, 306, 308) to the set current level whenever the controller 106provides a high level signal to it. PWM consists of high and low signalsat a fixed frequency. One could change the duration of high and lowsignals in a given time frame (defined as time period=1/frequency).Considering the controller sends one PWM signal to one LED driver tocontrol the average current through one associated LED arm. Varying theduty cycle of the PWM signal changes the average current flowing throughthe LED driver to the LED arm. The average current affects the overallluminosity of the II Device, such as that at lower average currentspassed through the LED driver then the II Device would be dimmer (i.e.,lowering the average currents passed through the LED driver dims thelight produced by the Device).

The II Device 140 might take other common embodiments not fullydescribed in this disclosure, but not limited to the following: (a) anII Device integrated into a lighting fixture (e.g., could be installedfixture with all II Device circuitries built in or non-installed fixturesuch as a plug in lamp); (b) an II Device integrated into a fan (e.g.,could be installed fixture with all II Device circuitries built in); (c)an II Device that is solely battery powered and affixed to a surface;(d) an II Device utilizing OLEDs as LEDs; (e) an II Device integratedinto directly into surfaces (walls, tables, and ceilings), clothing,appliances, electronics (Displays, music equipment, etc.), musicalinstruments (pianos, guitars, etc.) and taking power from some sourceeither internally or externally to that integrated part; or (f) an IIDevice specifically designed for emergency lighting. Considering thecontrol of the II Device, the invention herein provides processes andmethods to wirelessly control and/or program one or many II Devicesthrough one or many wireless devices. These processes and methods shownand described provide maximum utility and range with a givencommunication protocol and a reliable and efficient system.

Referring now to FIG. 2, a circuit diagram of a Single LED arm 214 withSingle LED(s) 122 in accordance with one embodiment of the presentinvention is shown. The LED arm 214 is electrically connected to thepower supply 200 and the LED driver 208. The power supply 200 and LEDdriver 208 are also connected to the ground or negative terminal 206 ofthe power supply 200. In certain embodiments, the controller/processor106 might send multiple PWM signals 210 to multiple LED drivers 208 tocontrol the current passed through to multiple LED arms 214. In thesecases, the LED current control circuit 120 would allow to similarlychange the overall brightness or luminosity of the II Device 140, butalso adjust the color and/or saturation of the light emitted from the IIDevice 140. In this latter case of controlling color and saturation theLED arms 214 would need to be of different colors that could createdifferent colors when mixed at different levels. The LED arm 214 canhave warm yellow or other colors/types of LEDs 122.

Now referring to FIG. 3, a circuit diagram of a Solely LED DriversScheme in accordance with one embodiment of the present invention isshown. For illustrative purposes, consider here four PWM signals (326,328, 330, 332) sent from the controller 106 annotated as PWM1 326, PWM2328, PWM3 330 and PWM4 332 and four associated LED drivers annotated asLED Driver1 318, LED Driver2 320, LED Driver3 322 and LED Driver4 324.In addition, consider four LED arms, LED arm1 302 with red LEDs 310, LEDarm2 304 with green LEDs 312, LED arm3 306 with blue LEDs 314, and LEDarm4 308 with white LEDs 316. Based on established color mixingprincipals, the variation in the luminosity of these four colors couldproduce all color combinations. To achieve this variation, thecontroller 106 could vary and alternate the length of time that the PWMsignals (326, 328, 330, 332) are sent to the LED drivers (302, 304, 306,308). This would create variations in lengths of time when the LEDdrivers (302, 304, 306, 308) would receive PWM signals (326, 328, 330,332). The length of time would also allow for a similar control in theoverall brightness of the luminosity produced by the II Device 140 inaddition to the control provided by variations of the duty cycle of thePWM signal itself.

Similarly, variations in the length of time that the controller 106would alternatively send each PWM signal (326, 328, 330, 332) to therespective LED driver (318, 320, 322, 324), which would control thecurrent passed through to the respective LED arm (302, 304, 306, 308),would also provide for a combinatory control of the average luminosityproduced by each LED arm (302, 304, 306, 308) and thus allow for controlof color and saturation of the light produced. The frequency of PWMsignals (326, 328, 330, 332) and the rate at which LED drivers (318,320, 322, 324) receive the PWM signals (326, 328, 330, 332) fromcontroller/processor 106 will be high enough (still within the LEDs' andLED Drivers' technical specifications) so that due to the persistence ofvision, consumers would see a constant light output, for example ayellow light instead of fast switching alternate red and green lightoutputs. The scheme in alternating PWM signals (326, 328, 330, 332) doesnot allow for simultaneous PWM signals (326, 328, 330, 332) executed bythe LED driver (318, 320, 322, 324) at the same time. This maximizes thepotential average current passed through LEDs arms (302, 304, 306, 308)and subsequent luminosity of each LED arm (302, 304, 306, 308)considering limited available current from the AC/DC converter 102. Itallows for each LED arm (302, 304, 306, 308) to receive the full powerprovided by the AC/DC converter 102 and regulated by the LED driver(318, 320, 322, 324), such that when it is on all the available currentcould be sent through to the one LED arm.

To further illustrate these concepts, below is an example of how thesolely LED driver scheme might work. Consider, the frequency of PWMsignal is 2 KHz or total time period for one signal (one high and onelow)=½ KHz=0.5 ms. Consider the duty cycle of each PWM1 400 and PWM2 402is the same. The higher the duty cycle, the brighter the overallluminosity would be and vice-versa. Each LED driver (318, 320, 322, 324)is designed for a particular current level, i.e. when LED driver (318 or320 or 322 or 324) is ON (when they get high signal from the controller106), the current passing through the LED driver (318, 320, 322, 324)would be the lesser value of either the designed particular currentlevel or the maximum current that power supply 200 can provide. Assumethat the luminosity created per unit of average current is the same forboth the red LED arm 302 and the green LED arm 304. If in 4 ms cycles,the controller turns on the PWM1 and turns off PWM2 every first 2 ms andthen turns off PWM1 and turns on PWM2 for the next 2 ms with PWM3 andPWM4 are off continuously, then, the overall light output would beyellow (mixture of Red and Green color light, each with sameluminosity).

Referring now to FIG. 4, a Timing Diagram for the solely LED driversscheme of FIG. 3 is shown. The clock signal 408 has a 0.5 ms time cycletime to produce a type of orange light which consists of 70% red and 30%Green light mixed together, PWM1/LED Driver1 400 should be ON for 70% ofthe cycle time (here, 70% of 4 mS=2.8 mS) and PWM2/LED Driver2 402should be ON for remaining 30% of the cycle time (here, 30% of 4 mS=1.2mS). Similarly, to produce brighter shade of orange light which mayconsist of 50% RED, 20% Green and 20% White light together, PWM1/LEDDriver1 400 should be ON for 50% of the cycle time (here, 50% of 4 mS=2mS), PWM2/LED Driver2 402 should be ON for 20% of the cycle time (here,20% of 4 mS=0.8 mS), PWM3/LED Driver3 404 should be ON for 0% of thecycle time (here, 0% of 4 mS=0 mS), PWM4/LED Driver4 406 should be ONfor 20% of the cycle time (here, 20% of 4 mS=0.8 mS), and all PWM/LEDDrivers (400, 402, 404, 406) should be OFF for the remaining 10% ofcycle time (here, 10% of 4 mS=0.4 mS).

In a similar way, by varying PWM signal duty cycle for four LEDs Drivers(318, 320, 322, and 324) for a given PWM ON/OFF time cycle (4 mS in anexample above), II Device 140 could produce any color with differentshades. When duty cycle is 100% i.e. 100% ON and 0% OFF, the PWM/LEDDriver1 400 and PWM/LED Driver2 402 are ON for 2 mS alternately everyPWM ON/OFF cycle of 4 mS, II Device 140 will produce highest possible(100%) luminosity for the Yellow light. Thus the output luminosity canbe varied by varying duty cycle of the PWM signals (326, 328, 330, 332)to LED drivers (318, 320, 322, 324), providing dimming feature to IIDevice 140.

The algorithm/program in the controller is such that, at a time only oneLED Driver (here, 400 or 402 or 404 or 406) is given a PWM signal. Thisparticular scheme is more useful when power supply has limited currentoutput capability. With such algorithm one could achieve maximumluminosity for any color possible. For example, let's assume a powersupply is rated at a maximum 15 V/1 A output and all LEDs have rating of1 A and LED drivers are designed for 1 A current. To achieve 100%luminosity output from RED LEDs, one has to pass 1 A current through REDLEDs Arm 302 continuously. In this case, LED Driver1 318 only will begiven PWM signal for entire 4 ms of the PWM cycle and that too at 100%duty cycle. As against in other design if all four LED drivers aredesigned for ¼th of the possible supply of current i.e. ¼×1 A=0.25 A,maximum current will never exceed 0.25 A through any LED arm, and willthus limit the output luminosity of that particular LED arm.

The Algorithm/Program makes sure that only one LED Driver (318 or 320 or322 or 324) has its PWM signal ON at a time. To produce colors, programgives turns ON PWM signals to LED drivers (318, 320, 322, 324) in aserial manner i.e. alternately, fast enough so that due to persistenceof vision, consumer sees the output light as a single defined colorinstead of flickering Red, Green, Blue or White lights.

Now referring to FIG. 5, a circuit diagram of Switches (500, 502, 504,and 506) and LED Driver 508 Scheme in accordance with one embodiment ofthe present invention is shown. In this scheme, the controller/processor106 would send a Pulse Width Modulation (PWM) signal to one LED driver508 which would control the average current flowing through it. Inaddition, there would be a switch for every LED arm between the LEDdriver 508 and each LED arm (302, 304, 306, and 308). The controller isconnected to each switch (500, 502, 504, and 506) and can send an on/offsignal for each. Considering an embodiment with four LED arms (302, 304,306, 308) and subsequently four switches (500, 502, 504, 506), thecontroller 106 would send a signal to control Switch1 500, Switch2 502,Switch3 504 and Switch4 506, while also sending a PWM signal to the LEDdriver 508 to allow current to pass through to the switches (500, 502,504, 506). Variation in the average current passing through the LEDdriver 508 controlled by variations in the PWM sent by the controllerwould increase or decrease the average current passing through to thesubsequent LED arms (302, 304, 306, 308), thus controlling the overallbrightness of the LEDs. The switches (500, 502, 504, 506) turning on oroff, would be able to create different colors and saturation produced bythe light. When a switch (500, 502, 504, and 506) gets high signal fromthe controller 106, it provides path for current to flow from LEDs inLEDs arms (302, 304, 306, 308) to LED driver 508.

Considering the embodiment contains red, green, blue, and white LED arms(302, 304, 306 and 308 respectively), based on established color mixingprincipals, the variation in the luminosity of these four colors couldproduce all color combinations. To achieve this variation, thecontroller could vary and alternate the length of time that the switchesare turned on. This would create variations in lengths of time when theLED driver 508 would pass through current to the LED arms and thuscreate variations in lengths of time when the LEDs produce light. Thelength of time would also allow for a similar control in the overallbrightness of the luminosity produced by the II Device 140 in additionto the control provided by variations of the duty cycle of the PWMsignal 518 itself.

Similarly, variations in the length of time that the controller 106would alternatively send each switch (500, 502, 504, 506), which wouldcontrol the current passed through from the LED arms (302, 304, 306,308) to the LED driver 508, would also provide for a combinatory controlof the average luminosity produced by each LED arm (302, 304, 306, 308)and thus allow for control of color and saturation of the lightproduced. The frequency of switch signals will be high enough (stillwithin the LEDs' (310, 312, 314, 316) and LED Driver's 508 technicalspecifications) so that due to the persistence of vision, consumerswould see a constant light output, for example a yellow light instead offast switching alternate red and green light outputs.

The scheme in alternating switch signals does not allow for simultaneousswitches being on at the same time. This maximizes the potential averagecurrent passed through and subsequent luminosity of each LED arm (302,304, 306, and 308) considering limited available current from the AC/DCconverter 102 in the power supply 200. It allows for each LED arm (302or 304 or 306 or 308) to receive the full power provided by the AC/DCconverter 102 and regulated by the LED driver 508, such that when it ison all the available current could be sent through to the one LED arm(302 or 304 or 306 or 308).

To further clarify the scheme, consider the following example. A yellowlight with no white light added into it can be produced by thecontroller turning Switch 1 500 ON and Switch 2 502 OFF and then Switch1 500 OFF and Switch 2 502 ON continuously at the same frequency, fastenough so that due to the persistence of vision, consumer sees it as ayellow light output instead of alternate Red and Green light output. LEDdriver 508 circuit can be designed for a particular current level i.e.it will regulate the flow of current through it to the set current levelwhenever the controller 106 provides a high signal to it. PWM (PulseWidth Modulation) 518 consists of high and low signals at a fixedfrequency. One could change the duration of high and low signals in agiven particular time (defined as time period=1/frequency).

An example of how this circuitry works will now be described.Assumptions: (1) frequency of PWM 518/608 set is 2 KHz, i.e. total timeperiod for one signal (one high and one low)=½ KHz=0.5 mS; (2) frequencyat which switches (510, 512, 514, 516/600, 602, 604, 606) are turned ONand OFF=250 Hz, i.e. total time period for switch to turn ON and OFF=1/250 Hz=4 mS; and (3) LED driver 508 is designed for 1 A current, i.e.when any switch (500, 502, 504, 506) and LED driver 508 is ON (when theyget high signal from the controller 108) current passing through it is 1A or maximum current that power supply 200 can provide, whichever isless. The user wants a Yellow light output at half the maximumluminosity possible, for which Red 310 and Green 312 LEDs should beilluminated equally by sending same amount of average current throughthem. Also for half the luminosity, the average current passing throughRED LEDs arm 302 and Green LEDs arm 304 should be half the maximumaverage current possible. This is achievable by turning Switches (510,512, 514, 516/600, 602, 604, 606/500, 502, 504, 506) ON/OFF and settingPWM 518/608 as in the timing diagram below. The power supply can providemaximum current of 1 A for any LED arm (302, 304, 306, and 308) at atime.

Switching frequency of 250 Hz (cycle of 4 mS): When Switch1 500 is ON,Switch2 502 is OFF letting current flow through only one arm at a time.Also, time for which Switch1 500 is ON and time for which Switch2 502 isON are equal, thus producing Yellow light as required. However, toproduce a type of orange light which consists of 70% Red and 30% Greenlight together, SIG1/Switch1 510/600 should be ON for 70% of the cycletime (here, 70% of 4 mS=2.8 mS) and SIG2/Switch2 512/602 should be ONfor remaining 30% of the cycle time (here, 30% of 4 mS=1.2 mS).Similarly, to produce brighter shade of orange light which consists of50% RED, 20% Green and 20% White light together, SIG1/Switch1 510/600should be ON for 50% of the cycle time (here, 50% of 4 mS=2 mS),SIG2/Switch2 512/602 should be ON for 20% of the cycle time (here, 20%of 4 mS=0.8 mS), SIG4/Switch4 516/606 should be ON for 20% of the cycletime (here, 20% of 4 mS=0.8 mS), and all switches (510, 512, 514,516/600, 602, 604, 606) are off for the remaining 10% of cycle time(here, 10% of 4 mA=0.4 mS). FIG. 6 is a timing diagram for the switchesand LED driver scheme of FIG. 5.

In a similar way, by varying the switching combinations for a given timecycle, II Device 140 could produce any color with different shades. Whenduty cycle is 100% i.e. 100% ON and 0% OFF, the LED driver 508 is alwaysON, thus letting current pass continuously through an LED arm (302, 304,306, 308) which has its switch ON, in turn providing highest possibleluminosity for the color produced. Thus the output luminosity can bevaried by varying duty cycle of the PWM signal 518/608 to the LED driver508, providing dimming feature to II Device 140. The algorithm/programin the controller 106 is such that, at a time only one switch or limitednumber of switches will be turned ON. Thus, making sure that maximumpossible current (mainly set by LED driver 508 circuit) flows throughthe LED arm of that particular switch at that time. This particularscheme is more useful when power supply has limited current outputcapability. With such algorithm one could achieve maximum luminosity forany color possible.

For example, let's say a power supply 200 (AC/DC Converter 102) is ratedat a maximum 15 V/1 A output. Let's assume all LEDs have rating of 1 A.To achieve 100% luminosity output from RED LEDs arm 302, one has to pass1 A current through RED LEDs arm 302 continuously. In this case,SIG1/Switch1 510/500/600 will be ON continuously and PWM 608 duty cycleto LED driver will be 100% as well. However, if one designs all four LEDdrivers to ¼th of the maximum supply current from AC/DC converter i.e.¼×1 A=0.25 A, maximum current will never exceed 0.25 A through any LEDarm, thus limiting the output luminosity of that particular LED arm andcombination of LEDs to be ON. Algorithm/Program makes sure that only oneLED arm is ON at a time, and to produce colors other than Red, Green,Blue and White, program turns ON/FF the respective switches fast enoughso that consumer sees the output light as a defined color due topersistence of vision.

Referring now to FIG. 7, a circuit diagram of a Multiplexer 704 and aLED Driver 508 Scheme in accordance with one embodiment of the presentinvention is shown. In this scheme, the controller/processor 106 wouldsend a PWM 518 signal to one LED driver 508 which would control theaverage current flowing through it. In addition, there would bemultiplexer 704 between the LED driver 508 and each LED arm (302, 304,306, and 308). The controller 106 is connected to the multiplexer 704via two signals. Based on SIG1 700 and SIG2702 signals, the multiplexer704 selects an LED arm (302, 304, 306, and 308) to connect to the LEDdriver 508 at a time producing light with different colors, saturation,and brightness. Variation in the average current passing through the LEDdriver 508 controlled by variations in the PWM 518 sent by thecontroller would increase or decrease the average current passingthrough to the subsequent LED arms, thus controlling the overallbrightness of the LEDs (310, 312, 314, 316).

Considering the embodiment contains red, green, blue, and white LED arms(302, 304, 306 and 308 respectively), based on established color mixingprincipals, the variation in the luminosity of these four colors couldproduce all color combinations. To achieve this variation, thecontroller 106 could vary and alternate the length of time that themultiplexer signals are turned on to let current pass through to each ofthe respective LED arms (302, 304, 306, and 308). This would createvariations in lengths of time when the LED driver 508 would pass throughcurrent to the LED arms (302, 304, 306, and 308) and thus createvariations in lengths of time when the LEDs produce light. The length oftime would also allow for a similar control in the overall brightness ofthe luminosity produced by the II Device in addition to the controlprovided by variations of the duty cycle of the PWM signal 518 itself.

Similarly, variations in the length of time that the controller 106would alternatively send signals to the multiplexer 704, which wouldcontrol the current passed through from the LED driver 508 to the LEDarm (302, 304, 306, 308), would also provide for a combinatory controlof the average luminosity produced by each LED arm (302, 304, 306, 308)and thus allow for control of color and saturation of the lightproduced. The frequency of signals sent to the multiplexer 704 will behigh enough (still within the LEDs' and LED Drivers' technicalspecifications) so that due to the persistence of vision, consumerswould see a constant light output, for example a yellow light instead offast switching alternate red and green light outputs. The scheme inalternating multiplexer signals does not allow for simultaneous signalsto allow current to pass to more than one LED arms at the same time.This maximizes the potential average current passed through andsubsequent luminosity of each LED arm (302, 304, 306, and 308)considering limited available current from the AC/DC converter 102. Itallows for each LED arm (302, 304, 306, 308) to receive the full powerprovided by the AC/DC converter 102 and regulated by the LED driver 508,such that when it is on all the available current could be sent throughto the one LED arm (302, 304, 306 or 308). The timing method is similarto that of the switches and LED drivers scheme (FIG. 6). The multiplexerscheme would vary dependent on the II Device 140 requirements and totalnumber of LED arms.

Now referring to FIG. 8, a circuit diagram of current limiting circuitscheme in accordance with one embodiment of the present invention isshown. In this scheme, current limiting circuits (800, 802, 804, and806) control the current passed through to each LED arm (302, 304, 306,and 308). There would be as many current limiting circuits as LED armsthat are required for the specific embodiment of the II Device. Thecontroller/processor 106 sends data to the individual current limitingcircuit (800, 802, 804, and 806) and defines the current to be passedthrough to the respective LED arm (302, 304, 306, and 308). A digitalpotentiometer could be used to form the current limiting circuit (302,304, 306, and 308). The resistance of potentiometer is proportional tothe data given to it by controller/processor 106.

For example, to produce a yellow light consisting of 50% Red and 50%Green light at 100% possible output luminosity, DATA1 808 and DATA2 810will set the currents through current limiting ckt1 800 and ckt2 802such that the current splits in half through two arms (DATA3 812 andDATA4 814 will be zero). For example, if power supply 200 is able toprovide 1 A current, ckt1 800 and ckt2 802 will be set at 0.5 A each.Considering the embodiment contains red, green, blue, and white LED arms(302, 304, 306 and 308 respectively), based on established color mixingprincipals, the variation in the luminosity of these four colors (310,312, 314, 316) could produce all color combinations. Setting assignedcurrents through all circuits (800, 802, 804, and 806), any color,saturation, and brightness within specified limits could be achieved. Inother embodiments, the light generator is composed of alternativelighting components and technologies including but not limited to CFLs,Halogen, and Incandescent.

Now referring back to FIG. 1, in some embodiments, the II Device 140might have an ambient light sensor circuit 118. The ambient light sensorcircuit 118 includes one or more ambient light sensors (photo sensor orsimilar light detecting component) and supporting circuitry. The ambientlight sensor(s) in the ambient light sensor circuit 118 detects a levelof captured ambient light, converts that level into an analog signal,and sends that data to the controller/processor via an analog to digital(A/D) converter that could be a part of the ambient light sensor circuit118 or controller/processor 106. The ambient light sensor circuit 118would consist of one or more ambient light sensors per one or multipleII Devices. In some embodiments the ambient light sensor circuit 118could be embedded in the II Device 140 itself and in others it might bea separate peripheral device to the wireless lighting control system.Additionally, the placement of the sensor(s) 118 and related circuitryneed not be exactly collocated, but possibly separated by a wire.

For example, the light sensor(s) 118 could be placed in multiplelocations in relation to the II Device 140: (a) placement of sensor 118requires external light to reach the light sensor; (b) the sensor(s) 118could be placed on the exterior of the light, on the housing; (c) thesensor(s) 118 could be at the end of an extension or wire protruding; or(d) the sensor(s) 118 could be part of an external peripheral to thelight, connected via wireless communication (e.g., the sensor could behoused with other electronic components such as a processor,communication source (Bluetooth module, Zigbee, Wi-Fi, or other)). Therecould also be multiple types of II Device sensors used: (a) one whichsenses a range of overall luminosity; (b) one that senses a combinationof red, green and blue components or cyan, yellow, magenta or blackcomponents, or hue, saturation and lumens components of the light on it;or (c) in different scenarios the light measured could be in absolute orrespective values. The ambient light sensor 118 can be located to detectan ambient light and a light emitted by the II Device 140 such that thecontroller/processor 106 adjusts one or more of the on/off signalsprovided to the LEDs 122. In one embodiment, the light detector includesa photo sensor and related circuitry. The photo sensor detects overalllight and changes therein and sends current data to the processor. Theprocessor in turn reads the data and takes subsequent action if needed.In other embodiments the light detector includes multiple photo sensorsor other means of detecting light. In other embodiments the light sensormight include an additional heat sensor.

In some embodiments, the hard reset circuit 116 of the II Device 140includes a button or switch mechanism and related circuitry. The buttonor switch would be connected to the controller/processor 106 eitherdirectly on the same board or through a wired connection. When thebutton or switch is activated, it will send a specific signal to thecontroller/processor 106 to execute the hard reset program for that IIDevice 140. The actual button or switch mechanism might be differentdependent on the II Device 140 and its application. As example, thereset circuit might be a simple resistant button type switch, it mightbe a rotational type switch, or it might be a conductive type switch, itmight be a compression switch based on pushing in some part of themechanical structure. The location of the hard reset circuit might beco-located with other external components such as the ambient lightsensor, LEDs, diffuser housing, or other II Device components orstructural parts. In this sense the physical location with respect tothe II Device 140 might vary. The hard reset function in mostembodiments will require access to the DC/DC power, and thus the IIDevice 140 would need to be connected to an active power source. In someembodiments though, the hard reset circuit 116 would have access to aseparate power source such as a battery to provide the controller andrelated circuitry enough power to execute the hard reset command.

The heat sink and related components and parts 124 may be required insome embodiments of the II Device 140. The heat sink and relatedcomponents 124 dissipate the heat generated by the LEDs 122 and LEDcurrent control circuit 120. The heat sink 124 could take multiplesizes, shapes, and materials dependent on the II Device embodiment.‘Related components’ refers to the housing and outer structure of the IIDevice 140. These materials and arrangement might of course differdepending on the particular II Device embodiment.

The diffuser 128 is a part of the II Device 140 that spreads and/or‘mixes’ the illumination produced by the LEDs 122. The diffuser 128could be made of different materials and come in different sizes,dependent on the specific variation and application of the II Device140. Common material might be glass, plastics, or fiber. The diffuser128 would be placed over the LEDs 122 so that the illumination passesthrough the diffuser 128. The exact placement, angle, and arc of thediffuser 128 related to the LEDs 122 would vary dependent on thevariation and application of different II Devices. The light enhancementcover is the lens or material above the LEDs that will focus and/ordisperse the emitted light for required ambience. The light dispersioncover may or may not be present in all embodiments and may take varyingforms and nature.

The light reflector 126 is used to amplify or focus the illuminationgenerated by the LEDs 122. The light reflector 126 could be made ofdifferent reflective materials and come in different sizes, dependent onthe specific variation and application of the II Device 140. The lightreflector 126 would be placed behind and/or around the LEDs 122, mostlikely at an arc so that the illumination of the LEDs 122 is reflected,focused, and amplified through the diffuser 128. The exact placement,angle, and arc of the light reflector 126 would vary dependent on thevariation and application of different II Devices.

Given the standard parts and connections of the II Device 140, therecould be numerous potential II Device embodiments with differingarrangements, combinations, or expressions of the components disclosed.Some of these embodiments, characteristics and methods will be describedbelow.

As previously mentioned, the II Device 140 could be modular (i.e.,different parts of the II Device 140 as separated by a dashed-dot linesA, B, C, D, E and F could be detachable from a manufacturing or consumerstandpoint). Certain parts or modules of the II Device 140 could beinterchangeable with other types of the same module. As example,consider an II Device 140 that has different connector modules, plug invs. Edison base, yet the rest of the modules are the same. The modulescould be connected together through connectors, that a user couldseparate or place back together. The modules might also be structurallyfixed together so that disassembly is required to disconnect themodules. Additionally, modules within the II Device 140 could beseparated physically from each other yet connected electronically insome fashion. There could be different levels of modularity or nomodularity at all, depending on the specific II Device embodiment.

Referring now to FIGS. 9 and 10, a mechanical diagram and a blockdiagram of a Smartstrip Light 900 in accordance with one embodiment ofthe present invention is shown. There could be numerous versions or likeembodiments, but the general description will be disclosed herein. TheSmartstrip 900 consists of the same arrangement and inclusion of all thecomponents of an II Device 140 as previously disclosed.

The Smartstrip 900 includes a flexible strip 912, an electricalconnector 908 affixed to the flexible strip 912 and two or more LEDs 122affixed to the flexible strip 912 and electrically connected to theelectrical connector 908. In addition, electrical circuitry 906 (AC/DCpower converter 102, controller/processor 106 and LED current controlcircuit 120) is remotely located with respect to the flexible strip 912and electrically connected to the electrical connector 908 via a wire, acable or a connecting strip. The LED current control circuit 120provides an on/off signal having a cycle time to each LED 122 inresponse to one or more control signals received from thecontroller/processor 106 such that the two or more LEDs 122 produce ablended light having a specified color based on how long each LED 122 isturned ON and/or OFF during the cycle time. As shown, the LEDs 122 areformed into LED Groups 1100 that may include a heat sink 124 attached tothe flexible strip 912, a reflector 126 disposed behind or around thetwo or more LEDs 122, and/or a diffuser or lens 128 disposed above thetwo or more LEDs 122. The LED Groups 1100 are connected in parallel orseries or a combination of both by electrical connections 914.

Other embodiments will include additional components. For example, theadditional components may include: a power supply connector/fastener100; an AC/DC power converter 102 electrically connected to the powersupply connector/fastener 100 and the DC/DC power converter 104; a realtime clock (RTC) circuit 110 communicably coupled to thecontroller/processor 106; a memory 108 communicably coupled to thecontroller/processor 106; a wireless transceiver circuit 112communicably coupled to the controller/processor 106; an antenna 114communicably coupled to the wireless transceiver circuit 112; a hardreset circuit 116 communicably coupled to the controller/processor 106;and/or an ambient light sensor circuit 118 communicably coupled to thecontroller/processor 106. These components were previously described inreference to FIG. 1.

The connector 100 could be one of many connectors that would provide aconnection to a power source. This could be an Edison base (multiplesizes), Plug in, Bi-pin, or Battery connected connection. The connectorwould conduct the electrical current to the AC to DC converter 102through an AC power cord 902, which is an electrical wire for carryingstandard mains power supply.

The AC to DC converter 102 receives power from the connector 100 andoutputs the appropriate DC power to the DC/DC converter(s) 104 and theLED current control circuit 120 and LED strip circuit 912. The AC to DCconverter 102 might be housed within the connector 100 or separate fromthe connector 100, depending on the specific Smartstrip embodiment.

The DC/DC converter(s) 104 receives a power input from the AC/DCconverter 102 and then converts that power to DC power(s) required fordriving the internal components/modules of the Smartstrip 900. Thesecomponents include the controller/processor 106, memory 108, the realtime clock (RTC) circuit 110, the wireless transceiver circuit 112,antenna 114, and possibly components within the LED current controlcircuit 120. It might also supply power to components, such as the hardreset circuit 116, the ambient light sensor circuit 118, and otherpotential added circuitries. There might be multiple convertersdependent on the output DC voltages required by different componentrequirements. Similarly, the power output would very dependent on theexact component requirements, for example the output might be 5 VDC, 3.3VDC, or 1.3 VDC.

The Controller/processor 106 processes signals received from the memory108, the real time clock (RTC) circuit 110, and the wireless transceivercircuit 112. It might also process signals from other components, suchas the hard reset circuit 116, the ambient light sensor circuit 118, andother potential added circuitries. It also takes action and sendscommands to the memory 108, the real time clock (RTC) circuit 110, andthe wireless transceiver circuit 112. It might also take action and sendsignals to other components, such as the ambient light sensor circuit118 and other potential added circuitries.

The memory 108 stores data from factory defined settings and from userdefined settings. The controller/processor 106 will read/write data inmemory 108. Data might include factory defined settings such ascommunication protocols, identification and security protocols, andother data. Data might also include user defined settings such as userprofiles, default commands, programs, and other data. The memory 108could be inside the processor 106 and/or external to the processor 106as a different IC. The controller/processor 106 and memory 108 circuitmight take a number of different technical specifications.

There are two types of potential LEDs strips—a regular LEDs strip and anextendible LEDs strip. The LEDs strip consists of electrically connectedLEDs Groups placed at some distance from each other on a flexiblematerial. For support, the strip might be fastened in some other manner(such as screws or adhesive) to a surface such as ceiling, wall, etc.

Referring now to FIG. 11, a circuit diagram of LEDs groups 1100 on aflexible LED strip 912 in accordance with one embodiment of the presentinvention is shown. Here, LEDs 122 are placed group-wise on a flexiblestrip 912 with some distance between them. The distance depends upon therequirements of the Smartstrip light requirements. Each LEDs group 1100might have an individual heat sink and diffuser (to mix colors, in caseof different types if colored LEDs in a group). Each LEDs group 1100 hasone or many LEDs 122 from each LEDs arm 1102 depending upon theSmartstrip light requirements. These LEDs 122 of a particular arm ineach group are electrically connected in a series or parallelcombination of LEDs depending upon the requirements of the Smartstrip900. The LEDs arms 1102 are connected to the positive terminal 1106 andthe negative terminal 206 of the AC to DC converter 102. In addition,the number of LEDs groups 1100 would depend upon the requirements of theSmartstrip 900.

Now referring to FIGS. 12A-1-12A-2 and 12B-1-12B-2, block diagrams of afront view and a rear view, respectively of a LEDs Strip 1224 andextendible LEDs strip 1226 in accordance with one embodiment of thepresent invention are shown. FIGS. 12A-1-12A-2 and 12B-1-12B-2 show thatLEDs groups 1100 are placed a flexible material 912 with some distancebetween them and connected together in series, parallel or a combinationof both with electrical connections 914. There could be an ambient lightsensor circuit 118 on the front of the LEDs strip 1224 and extendibleLEDs strip 1226 electrically connected to the electronic circuit 906.Also, there could be a connector 1200 on both the ends of the LEDs strip1224 and 1226 out of which one 1200 a is used to connect to theelectronic circuit 906 and the other 1200 b could be used to connect tothe extendible LEDs strip 1226. There could be PWM and/or switchingsignals from the controller/processor 106 that are used to drive currentcontrol circuit 120 on the regular LEDs strip 1224 and are carried tothe end connector 1200 b of the strip which could eventually be used todrive current control circuit 120 on extendible LEDs strip 1226. In thecase of using an extendible LEDs strip 1226 in addition to the regularLEDs strip 1224, the power requirement to drive total LEDs willincrease. That could be taken care by higher power supply ratings. FIGS.12A-1-12A-2 and 12B-1-12B-2 show that the strips 912 have adhesive(s) orfastener(s) 1222 to fasten the strip on a surface such as ceiling orwall. The strip 912 is made up of a flexible material so that it couldbe routed as required during the installation at the site of its use. Inaddition to the LEDs groups 1100 and other potential components as inregular LEDs strip (FIGS. 12A-1-12A-2), the extendible LEDs strip (FIGS.12B-1-12B-2) has its own current control circuit 120 to control averagecurrent through LEDs 122 on the strip (FIGS. 12B-1-12B-2).

Some Smartstrip 900 embodiments and embodiment versions might have anambient light sensor circuit 118. The ambient light sensor circuit 118may have one or more ambient light sensors (photo sensor or similarlight detecting component) and supporting circuitry. The ambient lightsensor(s) 118 detects a level of captured ambient light, converts thatlevel into an analog signal, and sends that data to thecontroller/processor 106 via an analog to digital (A/D) converter. Theambient light sensor circuit 118 would consist of one or more ambientlight sensors 118 per one or multiple Smartstrips 900 and/or II Devices140. In some embodiments the ambient light sensor 118 could be embeddedin the Smartstrip electronic circuit 906 board or on LEDs strip and inothers it might be a separate peripheral device to the wireless lightingcontrol system. Additionally, the placement of the sensor(s) 118 andrelated circuitry need not be exactly collocated, but possibly separatedby a wire 1206. In addition, some Smartstrip 900 embodiments andversions might have a heat sink(s) 124, a reflector 126 and/or adiffuser 128.

Referring now to FIG. 13, a block diagram of the mechanical andelectrical connections for the Smartstrip 900 in accordance with oneembodiment of the present invention is shown. The Smartstrip light 900has four parts: a connector 100, an AC/DC converter 102, an electroniccircuit 906 and LED strip 912. Any two parts could be connected by aflexible wire which would provide flexibility of distance between thetwo parts, routing of the Smartstrip 900 while placing it on thesurface. In addition, any two parts could be connected to each otherwith mechanically inflexible material; in fact combined parts could looklike one part. For example, connector 100, AC/DC converter 102 andelectronic circuit 906 parts could be closely connected to each otherand could look like one part.

Now referring to FIG. 14, a block diagram of an extendible LEDs Strip inaccordance with one embodiment of the present invention is shown. A LEDsstrip 912 a can be extended by connecting two or more LEDs strips 912 band 912 c. LED strip 912 a would have a connector 1400 at its ends whichwould be used to connect another strip 912 b to it. As shown in thefigure, LEDs strip 2 912 b is connected to LEDs strip 1 912 a and LEDsstrip 3 912 c by a flexible electrical extension 1402, such as anelectrical wire, with connectors 1400 on the ends of the LEDs strips 912a, 1912 b and 912 c. These connectors 1400 could be of various types,for example, male connector on the right end of the strip and femaleconnector on the left end of the strip. The connections 1400 includecurrent controlling signals from controller/processor 106 driving linesfor LEDs 122 on the strip 912 and LEDs driver signals. In addition, thestrip has LEDs current control circuit 120 to control current throughLEDs 122 as explained in the II Device section.

Referring now to FIG. 15, a block diagram of a LEDs strip 912 extensionthrough parallel connection in accordance with one embodiment of thepresent invention is shown. The extendable LED strip 912 has LED Groups1504 connected in series with an electrical plug-in connector 1500 viaelectrical connections 1502 (positive) and 1508 (ground), and anelectrical plug-in connector 1506 connected in parallel with the LEDGroups 1504 via electrical connections 1502 (positive) and 1508(ground). Electrical plug-in connectors 1500, 1506 are on the both endsof the extendable LED strip 912. On one end of the LED strip 912, therewould be an intake connector 1500 and on the opposite end of the LEDstrip 912 an outtake 1506 connector. The intake connector 1500 wouldplug into the outtake connector 1506 of the previous LED strip 912(either a regular or extendable LED strip) that would ultimately beconnected in sequence to a regular LED strip and the rest of theSmartstrip components and power source.

In addition to FIG. 15, now referring to FIGS. 16 and 17, block diagramsof a LEDs strips 912 direct connection in accordance with one embodimentof the present invention is shown. The intake connector 1500 would havemultiple electrical connections passing internally to the strip 912.There would be electrical connections 1502 to extend power through tothe LEDs groups 1100 in series. There would also be electricalconnections 1502 that would extend the power through to the otherouttake electrical plug-in connector 1506 on the opposite side of theLEDs strip 912. When this outtake electrical plug-in connector 1506 isnot in turn connected to another intake electrical plug-in connector1500 of another strip, the connection will terminate in the outtakeconnector 1506. The electrical connections 1502 would include groundconnection 1508 and current controlling signals such as PWM andswitching signals from the controller/processor 106 for both theconnection to the LEDs current control circuit 120, LEDs groups 1100 inseries, and the connection to the outtake connector 1506. Additional LEDstrips could be connected in the same fashion. This number of LED stripsconnecting to each other could be limited by the available power sourceand required current for each strip 912.

As shown in the FIG. 16, the outtake connector 1506 on one strip 912 acould be connected to the intake connector 1500 on another strip 912 bthrough an electrical wire 1604 with similar mating connectors 1600,1602 at its end. This type of connection provides additional flexibilityand routing while extending the number of strip in the Smartstrip. Asshown in the FIG. 16, the connecting wire 1604 might be an affixed partof the connector and Smartstrip or a separate part that could be used asneeded.

Now referring to FIGS. 18 and 19, a perspective view and explodedperspective view, respectively, of an Intelligent Illuminating Bulb 1800also referred as II Bulb in accordance with one embodiment of thepresent invention are shown. The II Bulb 1800 is a lamp or bulb likestructure embodiment of an II Device 140. There could be numerousversions or like embodiments, but the general description will bedisclosed herein. The II Bulb 1800 consists of the same arrangement andinclusion of some or all of the elements described above in reference tothe II Device of FIG. 1.

The II Bulb 1800 includes a housing 1802, a DC/DC power converter 104, acontroller/processor 106 electrically connected to the DC/DC powerconverter 104, a LED current control circuit 120 communicably coupled tothe controller/processor 106 and electrically connected to the DC/DCpower converter 104, and two or more LEDs 122 comprising at least afirst color LED and a second color LED electrically connected to the LEDcurrent control circuit 120. The DC/DC power converter 104, thecontroller/processor 106 and the LED current control circuit 120 aredisposed within the housing 1802, and the two or more LEDs 122 areproximate to or within an aperture 1804 of the housing 1802. A heat sink124 is disposed within or outside the housing 1802. A reflector 126 isdisposed within the aperture 1804 of the housing 1802 and around the twoor more LEDs 122. A diffuser or lens 128 seals the aperture 1804 of thehousing 1802. The LED current control circuit 120 provides an on/offsignal having a cycle time to each LED 122 in response to one or morecontrol signals received from the controller/processor 106 such that thetwo or more LEDs 122 produce a blended light having a specified colorbased on how long each LED is turned ON and/or OFF during the cycletime.

Other embodiments will include additional components. For example, theadditional components may include: a real time clock (RTC) circuit 110communicably coupled to the controller/processor 106; a memory 108communicably coupled to the controller/processor 106; a wirelesstransceiver circuit 112 communicably coupled to the controller/processor106; an antenna 114 communicably coupled to the wireless transceivercircuit 112; a hard reset circuit 116 communicably coupled to thecontroller/processor 106; and/or an ambient light sensor circuit 118communicably coupled to the controller/processor 106. These componentswere previously described in reference to FIG. 1.

The connector 100 would be an Edison base or bi-pin for which when theconnector is inserted into the appropriate light socket, the connectorwould provide appropriate contact to extend the power source into thebody of the II Bulb 1800. In addition, the connector 100 will providesome structural stability in fastening the II Bulb 1800 into a socket.In some alternate versions of the II Bulb 1800 the connector might alsobe a plug-in or battery powered connector. The physical location of theantenna 114 and/or wireless transceiver circuit 112 could be placed inmultiple physical locations related to the II Bulb 1800. For example, itmight be placed outside of the II Bulb 1800 or inside the II Bulb 1800.Placing it outside, might increase the range of wireless communicationfor the II Bulb 1800, especially when installed in locations with poorreception. Alternatively, the antenna 114 might be built into thephysical structure of the II Bulb 1800 or be part of the main boardinside the II Bulb 1800.

The LED current control circuit 120 executes commands from thecontroller/processor 106 to control the current passed through the LEDs122. The LED current control circuit 120 might take different formsdependent on the II Device embodiment 1800 as previously described. EachII Bulb 1800 would have some arrangement of LEDs 122 that could vary incolor and type (brightness) depending on different II Bulbs. Varioustypes of LEDs 122 would be placed on a LEDs board 136 in a spaced andarranged fashion and connected electronically to other circuitry asexplained earlier. The LEDs board 136 consists of electrically connectedLEDs 122 placed on a single surface. The combination of LEDs 122 couldbe of various types and various colors. For example, the LEDs 122 mightvary in color such as red, green, blue, and/or white LEDs. The LEDs 122might also vary in their maximum output luminosity. The combination ofilluminations of these LEDs 122 could produce various levels ofbrightness and/or color. LEDs 122 on the board would be arranged so thatthe light from them would mix well forming a uniform color and overalllight from the II Bulb 1800 would spread uniformly in at a particulardegree around the circumference of the diffuser 128. In addition, theLED board 136 might be combined or surround other circuitry such as thehard reset circuit 116 and/or ambient light sensor 118. For embodimentswhere this is the case, the LEDs 122 could take a different arrangementto accommodate for the placement of those circuitries.

Referring now to FIG. 20, a diagram of a LEDs Board 2008 in accordancewith one embodiment of the present invention is shown. As an example ofthe LEDs board arrangement, the white LEDs 2006 could be placed at thecenter of the LEDs board 2008 with red LEDs 2000 on the exterior andblue 2004 and green LEDs 2002 placed in between. In addition, there isan arrangement for electrical contacts 2010, 2012 on the LEDs board 2008at some place as shown. The arrangement can be used to connect sensorssuch as ambient light sensor of the ambient light sensor circuit 118 andthe rest switch of the hard reset circuit 116 on the on the II Device totheir respective circuitry that could be on the main board 134. Thearrangement might be on certain planes such as vertical, horizontal, anddiagonals. In addition, the proportional relationship in the number ofcertain color LEDs to other types could vary dependent on the lightemitted by the LED and the specific embodiment requirements.

II Bulb 1800 may consist of Hard Reset circuit 116 as explained earlier.The location of the hard reset circuit might be co-located with otherexternal components such as the ambient light sensor 118, LEDs 122,diffuser 128, or other II Bulb components or structural parts. In thissense the physical location with respect to the II Bulb 1800 might vary.Now referring to FIG. 55, a potential placement of the photosensor 5502and reset switch 5504 on the light mixing cover/diffuser 128, 5500 thatis on the top of LEDs board 2008 of II Bulb. The heat sink and relatedcomponents and parts 124 are required in some embodiments of the II Bulb1800. As explained earlier the heat sink and related components 124dissipate the heat generated by the LEDs 122 and LED current controlcircuit 120 and it could take multiple sizes, shapes, and materialsdependent on the II Bulb embodiment.

Other ‘related components’ refers to related parts required for thefitment of heat sink and parts required of the housing and inner orouter structure of the II Bulb 1800. These materials and arrangementmight of course differ depending on the particular II Bulb embodiment.

As explained earlier, there would be a diffuser 128 that is a part ofthe II Bulb 1800 that spreads and/or ‘mixes’ the illumination producedby the LEDs 122. There could be an ambient sensor, a part of ambientsensor circuit 118 and/or hard reset button, a part of hard resetcircuit 116 on the diffuser 128, in which case, the diffuser 128 couldbe transparent at that place. Also, the diffuser in that case, may havea through-hole arrangement for electrical and mechanical connections ofthe sensor and button to the II Bulb 1800. In the II Bulb as well, asexplained earlier, the light reflector 126 is used to amplify or focusthe illumination generated by the LEDs.

Considering the control of the II Device, the invention herein providesprocesses and methods to wirelessly control and/or program one or manyII Devices through one or many wireless devices. These processes andmethods shown and described provide maximum utility and range with agiven communication protocol and a reliable and efficient system.

With a wirelessly connected II Device, it will be important for thedevice application to understand the current status of each II Devicewithin the network. In addition, it would be beneficial for each IIDevice or an auxiliary wireless device to know the status and signalstrength of other II Devices within its proximity. This would provide abetter user experience and a more efficient lighting control system.

Now referring to FIG. 21, a flow chart of a status request/updateprocess for a wireless device or auxiliary device to II Device inaccordance with one embodiment of the present invention is shown. Thebasic process for a status request from the wireless device or auxiliarydevice shown by element 2100 would begin with block 2102. Upon a statusupdate defined event 2103, the device application will trigger a commandthrough the wireless device or auxiliary device to send a wirelesscommunication to all II Devices in the vicinity 2104. This command willthen get extended through the mesh network 2105 (see communication andmesh network processes for reference as needed). Upon receipt 2106, eachII Device will both respond to the command with the current status ofthat II Device 2108 and extend the responses of other II Devices via themesh network 2105. Upon receipt back by the wireless device or auxiliarydevice, the status information will be interpreted by the deviceapplication 2110 and either store the information in the deviceapplication memory as an input to execute further commands 2114, triggera second communication or command to the II Device network 2116, or takesome other action 2112. The process completes in block 2118.

Referring now to FIG. 22, a flow chart of a status update process for IIDevice to II Device in accordance with one embodiment of the presentinvention is shown. The basic process for an internal II Device networkstatus refresh from II Device to II Device shown by element 2200 wouldbegin with block 2201. Upon a status update defined event 2202, acommand will be triggered in one or many II Devices to send a wirelesscommunication to all II Devices in the vicinity 2204. This command willthen get extended through the mesh network 2205 (see below) as needed.Upon receiving status updates sent by other II Devices 2206, the statusinformation will be interpreted by the II Device (processor) 2208 andused to either store the II Device ID's received and some associateddata of the status in II Device's memory 2212, trigger a secondcommunication or command to the II Device network 2214, or take someother action such as reconciling time or program differences 2210. Theprocess for II Device to II Device completes with block 2216. Theprocesses described in part 2100 and 2200 could be executed in sometandem or integrated fashion dependent on the specific program or taskat hand.

Referring now to both FIGS. 21 and 22, the device application, auxiliarydevice, II Device itself and related II Devices and II Device networkcould update status information upon different defined events, timeperiods, or processes signified by 2101. For example, upon start-up orlaunch of the device application a command could be sent to gather thestatus information and subsequent layout of each II Device within thenetwork. As another example, after a defined time period while thedevice application is open, the wireless device could send a command togather the status information and subsequent layout of each II Devicewithin the network. As another example, given a different defined timeperiod, each II Device could send a command to gather the statusinformation and subsequent layout of each II Device within the network.As another example, during certain programs either actively runs throughthe device application or passively in the II Device network, either thedefined time period example or the different defined time periodexamples above could be executed at differing times to better suit theprogram or application. Or it could be any combination of the previouslydescribed examples.

The actual status of each II Device may include but not limited to thefollowing information: (a) the ID# and signal strength of other IIDevices within range; (b) the color and/or brightness at which the IIDevice is currently illuminated; (c) the status of programs, defaults,and profile information stored in the II Device's memory; and (d) thecurrent time/date as stored in the RTC.

There are a number of different potential processes and programs thatwould require the current status of the II Devices communicated. For thedisclosure of this invention, it will be assumed that the status of theII Devices will already be known if having the status of one or thenetwork of II Devices is generally required to execute the program orprocess. In many cases the process of obtaining the status of an IIDevice is included in description and drawings. In other cases, thestatus need not be required in the program or process.

Now referring to FIG. 23, a flow chart of a communication process from adevice to II Device in accordance with one embodiment of the presentinvention is shown through element 2300. The process begins with block2301. Given a wireless device (WD) is equipped with hardware and systemsto execute wireless communication protocols (Bluetooth, Wi-Fi, ZigBee,or any other wireless protocol) as well as an appropriate deviceapplication 2302, a user could send a lighting command to an II Deviceby selecting the command via the device application 2304. Upon theuser's selection of a command for a specific II Device, the deviceapplication would translate the user's requested command into a lightsetting command and the specific stored ID for the selected II Device2306. This light setting command would include instructions for thespecified II Device ID to execute such as on/off, color, brightness, ora program. The light setting command would be translated into theappropriate wireless communication protocol and wirelessly sent via thewireless device 2308. The II Device if in range of the wirelesscommunication or mesh network 2309 relay communication would receive theprotocol via the II Device's antenna 2310. The transceiver/receivercircuitry would decode the wireless protocol to find the light settingcommand and send that to the controller/processor 2312. The controllerwill execute that command with the respective II Device's relatedcomponents 2314. Upon successful execution, the II Device will respondthrough the appropriate wireless communication that it has executed thelight setting command 2316-2318. The process ends with block 2320.

Referring now to FIG. 24, a flow chart of a communication process from adevice to multiple II Devices in accordance with one embodiment of thepresent invention is shown referred to as element 2400. The processbegins with block 2401. Similar to the process of sending a lightsetting command from a wireless device to an II Device 2300, given anappropriate wireless device and device application 2302, a user couldselect a command for multiple II Devices via the device application 2402that would send a wireless communication through the wireless devicepertaining to multiple II Devices 2404, 2406, which could be extendedthrough the mesh network 2407. Upon receiving the wirelesscommunications 2408, the II Devices could decode 2410, execute thecommand 2412, and each respond to verify the command has been executedutilizing the appropriate communication methods shown as 2414-2416. Theprocess would end with block 2418.

Now referring to FIG. 23 as well as FIG. 24, similar to the process ofsending a light setting command from a wireless device to an II Device2300 and the process for sending a light setting command from a wirelessdevice to multiple II Devices 2400, a user could use multiple wirelessdevices or a combination thereof to send a command to one or multiple IIDevices. As long as the wireless devices have the appropriate wirelessprotocol and associated hardware, has some version of the deviceapplication with an authorized profile 2302, and is in range of the IIDevice (or mesh network), then the wireless devices could send a commandin the same way that one wireless device could, to one or multiple IIDevices.

Now referring to FIG. 25, an II Device 140 within a mesh network (alighting system) will be described. The ability for one II Device toreceive a wireless communication from a wireless device equipped withthe device application, and pass on the communication to another IIDevice to execute the command within the wireless communication. On abroader scale, having a network of II Devices be able to extend andrelay a wireless device's command to extend the signal range or gobeyond the limited number of devices it can communicate with directly orone-to-one. Additionally, have the II Devices within the network confirmthe execution of the command and possible automated or user guidedtroubleshooting steps.

Additionally, there are some unique processes with regard to theinvention presented here with regards to the extension of the network.In one embodiment, a signal is sent from the controller throughBluetooth or other signal to a transmitter in an II Device. Uponreceiving the signal, the transmitter will extend the command to theremaining light part, but also respond to the controller that the signalwas received. If a signal is not received back from an II Device thatwas intended to receive a signal, the controller (through a device)sends out another signal to all bulbs to pass on the previous signal tothe specific II Devices that did not respond. In other embodiments, whena signal is sent out to a series of II Devices, the signal is thenautomatically relayed to all other II Devices with a tag of the lightthat is relaying the message and any II Devices that had previouslyrelayed the message. Other possibilities exist to relay the message toensure all II Devices with a relative range from each-other.

Consider a wireless device (WD1) (2550, 2552, 2554) is equipped withhardware and systems to execute wireless communication protocols(Bluetooth, Wi-Fi, ZigBee, or any other wireless protocol) as well asthe installed device application. Each wireless communication system hassome limitation in terms of range (measured in meters or feet). WD1 2550can communicate with II Device1 2500, II Device2 2502 and II Device32504 directly, however, it cannot communicate with other II Devicesdirectly because of range limitation. WD1 2550 can communicate with IIDevice4 2506 by passing the commands and data through II Device3 2504.Similarly, by passing commands/data through II Device3 2504 and IIDevice4 2506, WD1 2550 and II Device5 2508 can communicate with eachother. In the diagram, WD1 2550 can communicate with each II Devicedirectly or through II Device(s). The diagram is an example of meshnetwork with which the controlling wireless device (WD1 in this case)can communicate with all II Device(s) able to communicate with eachother (communication paths are shown as 2516-2544 with obstruction 2546preventing direct communication with some wireless devices).

In diagram above the II Devices are divided in different network levelsas follow: (a) II Devices which are in direct vicinity of WD1 2550 arenetwork level 1 called as NWL1 where II Device1 2500, II Device2 2502,II Device3 2504 are NWL1 II Devices; (b) II Devices which are in thevicinity of NWL1 II Devices, but not in direct vicinity of WD1 2550 arenetwork level 2 called as NWL2 II Devices where II Device4 2506 is NWL2II Device; (c) II Devices which are in the vicinity of NWL2, but not inthe vicinity of WD1 2550 or NWL1 are NWL3 II Devices where II Device52508 and II Device7 2512 are NWL3; and (d) similarly, II Device6 2510 isNWL4 II Device.

The process for forming a mesh network will now be described. There aremultiple processes that the wireless device and network of II Devicescould communicate with each other to set-up a mesh network, dependent onthe size of the network (number of II Devices), the dispersion inlocation of the II Devices (power signal), and other factors. Theprocess would generally involve the wireless device communicating withall II Devices within its signal range, and having each II Device alsocommunicate to other II Devices within its signal range, with anultimate output sent back to the wireless device including the currentstatus and ID's of all II Devices in signal range for wireless deviceand each II Device within the network.

Consider the following as one example of how to establish the meshnetwork. WD1 2550 communicates with NWL1 II Devices and stores their idsand statuses in the memory 106 and creates a network among them. Each IIDevice also communicates with other II Devices and stores their ids andstatuses in the memory 106 and creates a network among them. WD1 2550then sends commands to NWL1 II Devices asking what other II Devices theycan communicate with and their ids and statuses. Each NWL1 II Deviceresponds to the commands and provides information on theirconnections/network with ids and statuses. WD1 2550 then sends commandsto NWL2 II Devices through respective NWL1 II Device to get theinformation on the II Devices in their network and their statuses. NWL2II Devices respond back to WD1 2550 through respective NWL1 II Devicewith their network information. WD1 2550 now has all II Device ids inits memory at NWL1, NWL2 and NWL3 levels. In the same fashion, WD1 2550continues to build its network map by sending commands to next networklevel II Devices (in this case, NWL4) through intermediary network levelII Devices and gets information on their network. This process wouldcontinue until either the wireless device receives information from alllights set-up within the device application or selected for a particularcommand, or until all II Devices that can be reached through the meshnetwork have been captured either directly or through the mesh networkto the wireless device.

Using the statuses and information from each II Device, the applicationdevice run on the wireless device 2550 would then create a map of theentire network, including what II Devices are connected to what IIDevice and each connection's signal strength, and store it into itsmemory 106. WD1 2550 can find out the most effective path to communicatewith a particular II Device in the mesh network depending upon thesignal strengths between WD1 2550 and that particular II Device andsignal strengths between WD1 2550 and other II Devices wirelesslyconnected to other II Devices and that particular II Device. E.g. indiagram above, signal strength 2544 between WD1 2550 and II Device8 2514is very low. This may cause communication errors between WD1 2550 and IIDevice8 2514. Therefore, WD1 2550 can chose to communicate with IIDevice8 2514 through II Device2 2502 as signal strength between WD1 2550and II Device2 2502 and that between II Device2 2502 and II Device8 2514is good, leading to less errors in communication. When a command is sentfrom the wireless device to an II Device through a mesh network, the IIDevice will respond to confirm the command has been executed in asimilar path or along a more effective path given any potential changesin the network based on any changes in terms of movement of wirelessdevice, signal strength, etc. The mesh network could be limited to NWL1or NWL2 or any other network level based upon the criticality ofapplication and different II Device embodiments.

Considering the fact that some types of communication protocol/methodshave a limit to the number of devices that can be connected or havecommunication among, the device application will intuitively take theseas input constraints to the formation of an optimal mesh network andpath for the wireless communication of a command. As example, if thewireless communication uses Bluetooth technology, there might be someconstraints. Considering a piconet topology (ad-hoc computer networkusing Bluetooth technology), a master Bluetooth device (Mostly aWireless Device or II Device in this case) can communicate with amaximum of seven Bluetooth devices at a time. Understanding thisconstraint, the wireless device(s) and II Devices could execute the meshnetwork process in such a way to optimize both the total number of IIDevices captured by the network and the path to send any specificcommand through the mesh network. This can be achieved by executing thestandard mesh networking process, and the device application consideringthe resulting map of the network to calculate and decide which specificII Devices to keep connected within the direct connection of thewireless device and which to keep connected through other II Devices.

Considering a case where more than seven II Devices are found within thevicinity of the wireless device, the device application after receivingthe initial network mapping would adjust which II Devices to directlyconnect to and which to connect to through another II Device to attemptto reduce the number of II Devices directly connected to the wirelessdevice. This would open up the ability of the wireless device to searchfor and connect to additional II Devices within initial proximity thatmight not have been able to connect before due to the limit of sevendevices. This process would be balanced to ensure those lights thatcould only connect through another II Device are also accounted for andsignal strength is at the highest possible levels. Note that thisconstraint might not be the case for all versions of Bluetooth topologyor technology.

The steps for forming a dynamic mesh network will now be described.Similarly to controlling multiple II Devices with multiple devices,multiple wireless devices, in this case, WD1 2550, WD2 2552 and WD3 2554could control one or many II Devices via the mesh network. Each wirelessdevice, in this case, WD1 2550, WD2 2552 and WD3 2554 would execute themesh network process in relation to its location as explained earlierwith reference to wireless device WD1 2550 and II Devices in itsvicinity at different network levels such as NWL1, NWL2 and NWL3.

Along the same lines, a dynamic mesh networking is required as awireless device (WD) can move from one place to another changing foritself the II Devices in NWL1 and possibly the II Devices in otherrelated network levels such NWL2, NWL3, etc. In the dynamic mesh networkprocess, the wireless device and II Devices follow the same process asexplained in the formation of mesh network, but the process is repeatedon a continuous basis. Specifically, the wireless device and eachrelated II Device would keep updating their individual network asexplained earlier after every defined time interval. Each II Devicewould also keep providing the ids and statuses of II Devices in itsnetwork to the wireless device(s) in a defined time interval. This timeinterval would vary from a few seconds to hours depending upon thecomplexity and criticality of the application being run, powerconsumption, dispersion of II Devices, and total number of wirelessdevices and II Devices in the network.

In some embodiments, the mobile device is a remote or other controller.In other embodiments there could be an additional separate controller inaddition to a remote. In other embodiments there could exist a signalrelay device between the controller application/controller device andthe II Device. As an example, this could entail a simple Bluetooth toBluetooth exchange to extend the signal range, or it could also includea WiFi to Bluetooth adapter for remote access and control.

In FIG. 25, accessing an II Device network through various devices inaccordance with one embodiment of the present invention is shown aswell. Different types of wireless devices could work together to form,extend, and translate different communication methods to support themesh network. These different wireless devices could be standardwireless devices such as smartphones, tablets, computers, or otherstandard controlling wireless devices with the device applicationloaded. Alternatively, these different wireless devices could be anauxiliary device with some specialized or standardized deviceapplication to either perform a specific function or general function inrelation to the mesh network.

As example, a wireless device located outside of direct contact with thelighting network, but within range to another wireless device withinrange of the lighting network, could send commands through the wirelessdevice to the lighting network and subsequent mesh network. In thiscase, the remote wireless device RD 2548 would originate the commandsand then the localized wireless device WD1 2550 would act as the firstnetwork level of the mesh network. Note that the communication methodbetween the remote wireless device RD 2548 and the localized wirelessdevice WD1 2550 might be different than the communication method betweenthe localized wireless device WD1 2550 and the II Devices lightingnetwork. As an example, the remote wireless device RD 2548 maycommunicate with the localized wireless device WD1 2550 via an Internetbased protocol while the localized wireless device WD1 2550 communicateswith the lighting network via a Bluetooth protocol. Also, remotewireless device (RD) 2548 could be another embodiment of II Device 140.

Additionally, the remote wireless device RD 2548 might send acommunication to the localized wireless device WD1 2550 to send aspecific communication to the lighting network upon some defined event.In this, there might be a large passage of time between when thelocalized wireless device WD1 2550 receives the communication from theremote wireless device RD 2548 and when the localized wireless deviceWD1 2550 sends a communication to the lighting control system. In thisexample, the remote wireless device RD 2548 need not necessarily beoutside of the range of the lighting control system. The wireless deviceWD1 2550 may also act as a specialized auxiliary wireless device such asan external ambient light sensor and communicate with other wirelessdevices.

The Real Time Clock inside of each II Device would need to beperiodically updated to ensure accuracy. To achieve this, the deviceapplication on the wireless device would refer to and share its owncurrent date and time information via the wireless communication andconnection process—either as part of the status update process or analternate process. Additionally, the II Devices themselves can updateand reconcile discrepancies within the date/time without the wirelessdevice itself being present in the network. The actual process to updatethe date/time setting of the RTC in an II Device from the wirelessdevice/device application might be executed in a number of differentways.

The following are potential but not limited to all examples of how adevice to II Device date/time update process would be triggered,generally represented as element 2602 (FIG. 26). The wirelessdevice/device application might send the date/time setting upon everycommand sent to the II Device network, and when received the IIDevice(s) would update the current date/time setting in the RTC andstore latest update date/time in the II Device's memory. The wirelessdevice/device application might periodically over some time or number ofprocesses send the date/time setting upon every command sent to the IIDevice network, and when received the II Device(s) would update thecurrent date/time setting in the RTC and store latest update date/timein the II Device's memory. The wireless device/device application mightsend the date/time setting only when specific programming commands aresent or active that requires information from the RTC and store latestupdate date/time in the II Device's memory. The wireless device/deviceapplication might send the date/time setting after some time setting ischanged within the wireless device/device application. Further, anycombination of the above might be applicable.

Similarly, the process where II Devices share and reconcile date/timesettings might be executed in a number of different ways. The followingare potential but not limited to all examples of how an II Device to IIDevice date/time update process would be triggered, collectivelyrepresented as element 2702 (FIG. 27). The II Devices might share andreconcile their date/time at some multiple of when their status isshared. The II Devices might share and reconcile their date/time onlywhen executing certain commands or processes. The II Devices might shareand reconcile their date/time after some defined period of time. The IIDevices might share but only reconcile their date/time when they aredifferent. The II Devices might reconcile the date/time based on themost recent update of date/time setting. Further, any combination of theabove might be applicable.

Now referring to FIG. 26, a flow chart of a wireless device updatedate/time process in II Device in accordance with one embodiment of thepresent invention is shown and referred to as element 2600. The actualreconciliation process and dependency in commands would proceed asfollows, beginning with block 2601. When a wireless device update occursas previously referred to as 2602, the II Device receives the date/timestatus update 2602, the wireless device sends a date/time update to anynumber of II Devices within range 2604 or through the mesh network 2605.When the II Device will update and match its internal time via the IIDevice's RTC and memory 2608, 2610. The II Device's memory will alsoupdate the date/time value as the original date/time when the RTC wasupdated 2608, 2612. The II Device would then confirm the execution ofthe date/time update back to the wireless device 2614, 2616. In somecases, the wireless device might execute a troubleshooting process ifnot all II Devices confirm execution of the date/time status update2618, 2620. The process would conclude with block 2622.

Referring now to FIG. 27, a flow chart of an II Device update date/timein II Device in accordance with one embodiment of the present inventionis shown and referred to as element 2700. The process begins with block2701. When an II Device to II Device event occurs as referred topreviously as 2702, either through a status update or solely a date/timecommunication, the II Device(s) would send a date/time communication outto any II Devices either directly within range 2704 or within rangethrough the mesh network 2705. When a II Device receives the date/timecommunication from another II Device 2706, the receiving II Device willcompare the receiving date/time update to its own date/time status inthe RTC 2708. If the received date/time communication was set morerecently than that of the II Device's 2710, then the receiving II Devicewill update and match its internal time via the II Device's RTC andmemory 2714, 2716. The II Device's memory will also update the date/timevalue when the RTC was updated 2714, 2718. If the values are the same orthe received date/time was updated later than the receiving II Device'sinternally stored date/time 2710 to 2712, then the II Device takes noaction 2712 and will complete the II Device to II Device date/timecommunication process 2720. Considering a mesh network system wherethere are numerous paths and scenarios, broadly the II Device'sthemselves will only update their date/time when the received date timeoriginated from a more recent date/time update. Originated refers to thespecific date/time when a wireless device sends an update to the IIDevice(s). If an II Device then passes that date/time on to another IIDevice, the originated date would still refer to the original date/timewhen the wireless device sent the update to the II Device(s).

The control application part of the solution is a software applicationto manage, automate, program, and control a light or series of lightparts through the chosen communication protocol. In one embodiment, thesoftware application is a downloadable application on a mobile devicesuch as a smartphone, tablet, or computer. The application uses aninteractive and flexible user interface to receive the user's command.The commands are then communicated through the chosen communicationprotocol to one or many lights.

The iLumi LightScape can be used on any number of Bluetooth enableddevices, like a Smartphone or tablet, to control, program, and automatethe color and brightness of any individual II Devices or grouping of IIDevices. The solution provides the highest level of flexibility topersonalize the color, atmosphere, and mood of a room to better fit onespreference, time of day, or occasion at hand.

Referring now to FIG. 28, a flow chart of basic control areas inaccordance with one embodiment of the present invention is shown andrepresented by element 2800. Using the device application on a number ofdifferent wireless devices, a user could communicate and control thewireless lighting system in a number of ways. A user could control asingle II Device, a combination of II Devices, a predetermined group ofII Devices, multiple groups of II Devices, and the whole set-up ofnetworked II Devices. Control pertains to adjusting brightness, color,running a program, or setting a program to run at a future time or uponsome event. All processes begin with block 2801 and continue as follows:

Controlling a single II Device through the application: (a) a user willnavigate through screens on the application to select 2802 an individualII Device (e.g., can arrive by ‘drilling down’ into a group or selectingthe unique II Device to control); (b) once the single II Device isselected 2804, the device application will display potential options forcontrol 2806; (c) potential options for control include but are notlimited to the following collectively signified by 2808: (i) turningon/off to default, (ii) changing brightness, saturation, and/or color,and (iii) running a program now or upon some condition such as time.Alternate options for user customization include but are not limited to:(i) adding the II Device to an existing or new group, (ii) viewing theII Device's group assignments, (iii) viewing a hierarchy of programs andscenes that the II Device is included in, and (iv) troubleshooting theII Device. Once a user has selected the option for control, the deviceapplication will interpret the selection into a light control settingfor the selected II Device 2810 and send a wireless communication viathe appropriate processes, represented here collectively by element2812. As such, once the individual II Device receives the communication,it will then interpret the instructions and execute the command, thenrelay confirmation back to the wireless device per the appropriatecommunications processes.

Controlling multiple II Devices through the application: (a) a user willnavigate through screens on the application and select multiple IIDevices 2802 (e.g., can arrive by ‘drilling down’ into a group orselecting the unique light IDs to control; (b) once the II Device IDsare selected 2814, the user will be given options for control 2816; (c)potential options for control include but are not limited to thefollowing collectively signified by 2818: (i) turning on/off to default,(ii) changing brightness, saturation, and/or color, and (iii) running aprogram now or upon some condition such as time. Alternate options foruser customization include but are not limited to: (i) adding the IIDevice to an existing or new group, and (ii) troubleshooting the IIDevice. Once a user has selected the option for control, the deviceapplication will interpret the selection into a light control settingfor the selected II Devices 2810 and send a wireless communication viathe appropriate processes, represented here collectively by element2812. As such, once the individual II Device receives the communication,it will then interpret the instructions and execute the command, thenrelay confirmation back to the wireless device per the appropriatecommunication processes represented by 2812.

Controlling a group or multiple groups of II Devices through theapplication. A user will navigate through screens on the application andselect a group or multiple groups of II Devices 2802. Groups of IIDevices will be user configurable combinations of individual II Devices.They will most closely relate to rooms, but can have multiplecombinations. A specific scene is considered a specific command(s) givento a group of II Devices. Once the group 2820 or groups 2826 areselected, the user will be given options for control 2822, 2828,including but are not limited to the following collectively representedas element 2824 for a group or 2830 for multiple groups: (i) turningon/off to default, (ii) changing brightness and/or color, (iii) runninga program now or upon some condition such as time, and (iv) turningon/off a program that is set to run in the future or upon somecondition.

Alternate options for user customization include but are not limited to:(i) drilling down into individual II Devices for control, (ii) addingthe group to an existing or new group, (iii) viewing a hierarchy savedsettings, programs, and scenes that the group is included in, and (iv)troubleshooting the group. Once a user has selected the option forcontrol, the device application will interpret the selection into alight control setting for the each II Device within the selected groupor groups 2810 and send a wireless communication via the appropriateprocesses, represented here collectively by element 2812. As such, onceeach II Device within the selected group(s) receives the communication,it will then interpret the instructions and execute the command, thenrelay confirmation back to the wireless device per the appropriateprocesses, represented here collectively by element 2812.

Controlling a whole network of lights through the application is similarin fashion to controlling multiple groups, represented by a similarsequence of elements 2802, 2832, 2834, 2836, 2810, and 2812. All basiccontrol processes end at block 2838.

Programming is a process by which an II Device, multiple II Devices, agroup, or multiple groups can execute a command or sequence of commandsgiven some other event occurs or condition is met. Similarly, an IIDevice, multiple II Devices, group, or multiple groups could be given asequence of commands to execute in sequence at some time interval.Unique to the invention disclosed, a user can create programmedcommands, send them wirelessly to any number of specified II Devices,and the command would execute given a condition being met. The conditionwill generally be related to time, but many types of conditions could beinterpreted into time-based activities. For example, wireless devicesable to access the Internet provide a wealth of potential conditionsthat could be converted to time passed or the wireless device couldpassively monitor the condition and send a command when met.

Generally a condition could be executed through these sources: (a) thewireless device sends a command to any number of II Devices to execute aprogram given a date/time passing or date/time being met (e.g.,simulated sunrise, timer, etc.); (b) the wireless device sends a commandto any number of II Devices to execute a program given some otherconditionally based input directly available to the II Device (e.g.,ambient light sensor program); (c) the wireless device sends a commandto any number of II Devices to execute a program with the conditionbeing met at that time and the action stored in the II Devices memory(e.g., reset process); (d) the wireless device sends a command to anynumber of II Devices to execute a program with the condition being metat that time and the action specified through the command (e.g., starrynight); (e) the wireless device sends a command to any number of IIDevices to execute a program given some other conditionally based inputavailable to the lighting control network is available to said IIDevices (e.g., auxiliary ambient light sensor program); (f) the wirelessdevice sends a command to any number of II Devices to execute a programin coordination with wireless communications/commands providedsequentially through the device application (e.g., music sync); (g) thewireless device runs a program to monitor some condition and upon thatcondition being met sends a command to any number of II Devices toexecute a specified command or sequence of commands (e.g., weatheralerts); (h) any combination or sequential representation of the aboveprogram types.

Creating a program involves similar processes to basic control. A userselects an II Device, multiple II Devices, group, or multiple groups torun a program. The user then selects a program to be run by the selectedII Device(s): (a) there could be predefined suggested programs based onthe items selected (e.g., stored in device application memory); (b) theuser could create their own program; (c) each program will consist of atleast one command to be run when one or more conditions are met, ormultiple commands to be run sequentially or upon further conditionsbeing met (e.g., user to set/select condition); (d) the program can berun at that time or saved to run at a future time (e.g., the program canbe set to repeat on certain dates/times, such as days of the week, everyX days, or any time lapse interval). The command or series of commandsis then sent via the wireless network to each associated II Device(s).This is done through the appropriate wireless communication process.Each II Device(s) then interprets the command or series of commands,executes the command, or stores the command in memory to be executedwhen conditions are met. Similarly, each II Device(s) would confirm theprogram command via the appropriate communication method process.

Now referring to FIG. 29, a flow chart of a programming process inaccordance with one embodiment of the present invention is shown andreferred to as element 2900. Once a program or programs are saved a usercan recall and toggle those programs on/off. The process begins withblock 2901. At the main level of the device application 2902, there willbe a ‘programs’ button. When selected 2904 this will display allprograms associated with the active profile. Each program will be listedwith their current status as active vs. inactive. The programs will besorted based on active vs. inactive status with active listed first.Secondly, the programs will be sorted based on the proximity of theassociated II Devices to each program 2906. When toggled on 2908, theapplication will send the command or series of commands via the wirelessnetwork to each associated II Device(s) 2910 through one or moreappropriate communication processes, collectively represented here as2912. The actual light setting associated with the program might bestored in device application so that the wireless communication is toexecute a specific program type command. The actual light setting mightalso be stored in the II Device itself 2914 so that the deviceapplication/wireless device only requests the II Device to run thatprogram. Each II Device(s) then interprets the command or series ofcommands and their related program conditions, executes the commandgiven a present condition, or stores the command in memory to beexecuted at a later condition time or event. In the latter case, oncethe condition is met the II Device(s) will execute the program command2918. Then if there are further conditional commands within the program2920, the II Device will continue to monitor for conditions until theyare met 2916 and the II Device similarly follows the process to executethe program command 2918. Once no further conditional commands are inthe program 2920, the program completes and changes to inactive status2922 so that the program commands are deleted from the memory of eachrelated II Device, and the program returned to an off status in thedevice application 2924. Alternately, a program that was set to run canbe turned off 2926 so that the wireless device sends a command to therelated II Devices to not execute the conditional command prompted bythe program 2928. This command would be communicated through one or moreappropriate communication processes, collectively represented here as2912. When received, each II Device would change the program to completeand change it to inactive status 2922 so that the program commands aredeleted from the memory of each related II Device, and the programreturned to an off status in the device application 2924. The programmight still be saved in the device application memory for future use, ifa saved program. The program run process ends in block 2930.

In the case where program commands would overlap with each other, thedevice application will prompt the user to confirm the programselection. In such case, the selected program will overlap anyconflicting previously activated program. Alternatively, if the programcommands originated from multiple devices or profiles, the II Deviceswill execute programs in the order of profile hierarchy. Alternatively,the programs might execute in the order of the last received command.

The combination of the light and application allow for one to do amultitude of processes in unique home lighting and automation. Novelprograms include but are not limited to a simulated sunrise with analarm clock or atomic clock, underwater ocean wave with oscillating bluelights, spotlighting of a series of lights in a chosen manner, twinklingof lights, lighting synced to the rhythm timber and bass of music, andvarious other light themes.

Scenes & suggested scenes will now be described. A scene is a predefinedsetting or program related to multiple II Devices and/or groups, so thatwith one user selection any or all II Devices would execute a specifiedsetting or program. This element is useful to support very holisticfunctional lighting like turning off all II Devices before going to bed,turning on some II Devices to walk to the bathroom, setting a mood fordinner or a movie, or many other personal preferences. A scene iscomprised of a defined light setting and/or program for each of anynumber of individual II Devices and/or any number of groups. When ascene is activated, the device application recalls the defined lightsetting(s) and/or program and the associated II Device(s)/group(s) andsends a standard wireless command to each.

Referring now to FIG. 30, a flow chart of a process for creating a scenein accordance with one embodiment of the present invention is shown. Thescene control selection can be both suggestive and user configurable. Auser could drill into each established scene to view or edit the statesfor each II Device, add more II Devices, etc. A user could also select ascene to be run at a previous time such as through an automationprogram. Scenes might display graphically in the user interface with themost used scenes or the scenes containing the II Devices with theclosest signal strength higher in order. Users could also drag and dropthe order of scenes displayed to their preference.

Once a network of II Devices is set-up, the application might suggestsome pre-configured scenes dependent on the number of II Devices set-upwithin the network and the names of the groups (most likely rooms) thatwere assigned. More specifically, the device application would refer tothe list of groups configured by the user, and if certain predefinedkeywords or combinations of words were found within those groups, theapplication would suggest/show a scene related to that group or groupsin the scene options. Also, the device application would refer to thenumber of II Devices, the number of groups, and the number of II Deviceswithin each group to create suggested/predefined scenes. With more IIDevices, groups, and II Devices within groups, more complex scenes couldbe suggested, or more group specific scenes could be suggested. Allnumber of II Devices would include scenes all off and all on related toturning all II Devices off within the addressable network, or turningall II Devices on. As example, for any lighting network containing agroup of lights with the word “TV”, “Television”, “movie”, “film”, orrelated word, the application would suggest a lighting scene related towatching a movie, such as a soft blue light emitted from each of the IIDevices. The types of suggested scenes could vary dependent on differentapplications.

Through the device application, the user can create a new scene,referred to as element 3000 and beginning in block 3001, by firstselecting the option to create a scene in the device application 3002and selecting any number of II Device(s) and/or group(s), with which tostart creating the scene 3004. The user would then select/create thelighting control setting or program for the selected II Device(s) and/orgroup(s). Here, the light setting might be a previously user savedconfiguration, an automated application suggested configuration, or anewly created configuration 3006. Once selected, the user would thenhave the option to add additional subsets of II Device(s) and/or groupsto the scene 3008, which would revert back to a similar configurationprocess for that selection 3004, 3006. Once the user has configured allthe II Device(s) and/or group(s) that they wish 3008, the scene,comprised of any combination of II Device(s) and/or group(s), each witha specified light setting or program, will be saved and the user couldassign a specified name 3010. This information will be stored in thedevice application memory 3012 and the process will end in block 3014.

Note that each II Device within the scene is able to have a different IIDevice brightness and/or color. In addition, pre-defined programs for IIDevice(s) can also be run or activated through a scene in combinationwith a specific type of lighting to be executed at that time. Forexample, a ‘time to sleep’ scene might turn off all the II Devices inthe network, except for one II Device on very low blue light in achild's bedroom, and activate the II Device alarms for all bedrooms inthe house for a certain time. Once the user has selected the II Devicesand lighting output, the user can save that scene for future use asreferred to previously in 3010. The scene is saved within the deviceapplication memory 3012.

Now referring to FIG. 31, a flow chart of a process for executing ascene command in accordance with one embodiment of the present inventionis shown as element 3100. The process begins in block 3101. To turn ascene on, when the device application is open 3102, the user wouldselect (switch on) the desired saved (or suggested) scene as an optionpresented in the device application interface 3104. The deviceapplication would then retrieve and convert the scene selection intospecific light setting commands and/or programs to be executed by eachof the related II Devices in the scene 3106. The wireless device wouldthen convert the series of II Device light setting commands or programsinto the appropriate wireless communications directed at each of therelated II Devices within the group 3108 following standardcommunication methods/processes. Upon receipt, each II Device wouldexecute its related light setting command or program and send theappropriate wireless communication back to the wireless device toconfirm execution of the scene 3110 following standard communicationmethods/processes. The process completes in block 3112.

Changing and adding unique groupings of II Device (Setting up your owngroups) allows for user configurable set-up, alteration, and assignmentof any number of II Device combinations of the addressable lightingnetwork. Within the device application, each II Device has its ownunique ID. Through the application a user can combine any number of IIDevices and or existing groups together to form a group of II Devices.This can be done through user gestures (dragging and dropping),selecting an individual and assigning to a group, or through theeasy-setup program. Once any number of lights is assigned into a group,a user can select commands to all II Devices within the group by simplyselecting the group.

Referring now to FIG. 32, a flow chart of a process for creating a newgroup or adding to an existing group in accordance with one embodimentof the present invention is shown as element 3200. The process beginswith block 3201. A user selects any number or combination of II Devicesand/or groups through the device application 3202. The user then selectsthe option to either create a new group from the selection or add theselection to an existing group 3204. If creating a new group fromselection 3206: (i) then the user will need to name the group 3208(e.g., the device application might have a list of predefined namingconventions that a user has the option of selecting 3210, or they cantype their own); (ii) the user would then be prompted through the deviceapplication to set a group default light setting for all II Deviceswithin the group 3212 (e.g., a user could select different unique lightsettings for each II Device within the group that are all saved underthe group light setting (see default process for more details); (iii) asthe user is selecting the group default light setting, if in proximityto the actual lighting network the wireless device would adjust therelated II Devices to execute the light settings as the user is togglingdifferent options while selecting a default group setting 3214; (iv)once a user selects and sets the group default light setting 3212, thenthe group setting could be saved 3216 to the device application's memoryto be run in the future 3218 with the process ending in block 3224. Foradding the selection to an existing group 3220: (i) the user would thenselect what group to add the selection to via the device application3222; (ii) the user would then be prompted to confirm extension of thedefault group setting to the newly selected II Devices/groups or createnew light settings for the selected II Devices within the group 3212;(iii) as the user is selecting the group default light setting, if inproximity to the actual lighting network the wireless device couldadjust the related II Devices to execute the light settings as the useris toggling different options 3214; and (iv) once a user selects andsets the group default light setting 3212, then the group setting couldbe saved 3216 to the device application's memory to be run in the future3218 with the process ending in block 3224.

Now referring to FIG. 33, a flow chart of a process for executing agroup command in accordance with one embodiment of the present inventionis shown as element 3300. The process begins in block 3302. User selectsgroup(s) 3304 and related light setting command/program 3306 through thedevice application user interface. The application then identifies theII Devices assigned to the selected group through internal memory 3308.Wireless device running application sends commands through wirelesscommunication for those specified II Devices in the group 3310 followingthe appropriate communication methods/processes. Each II Device receivesand executes the intended light control setting or program 3312. Each IIDevice responds to the wireless device to confirm execution of the groupcommand 3314 following the appropriate communication methods/processes.Upon receipt of all confirmations the device application would updatethe group to ‘active’ or ‘on’ in the user interface 3316 with theprocess ending in block 3318. Note that any individual II Device can beassigned to multiple groups. Multiple groups can be combined, adjusted,or used to create new groups. Also note that in some scenarios not allII Devices assigned to a group could be accessed due to signal rangelimitations or other problems. In these cases, the user would still havethe ability to control those II Devices that are accessible at thattime. Similarly, a notation could be made in the user interfacesignifying a group that is not fully accessible.

A process will now be described for setting, using, and changing defaultlight levels for any number of II Devices (including switching on/offthrough wall switch), so that a user can easily customize, save, andrecall their standard lighting preference. Additionally, a processallowing for anyone to turn on the preset default of the II Devices,without using the application will also be described. Each II Devicewill always have an associated default light level. Each II Device mighthave multiple related default light levels with the following framework:(i) Manufacturing default—for each II Device the most basic lightsetting stored in each II Device's internal memory. The manufacturingdefault light setting will always be stored in the II Device's memory.(ii) Light default—for each II Device, the active default light settingthat will be executed when the II Device is turned on directly as in theprocess steps of 2800 to 2804 to 2838 (not through a group command) orupon power restoration (see power restoration mode below). Each IIDevice can only have one light default. This default light setting isstored within each II Device's memory until the II Device is reset orthe light default is changed. When unassigned, the light default revertsto the manufacturing default. (iii) Group default(s)—The light settingthat will be executed by each II Device within the selected group whenthe selected group is turned on through the device application. Thegroup default is stored within the device application related to eachgroup. Each II Device is able to execute multiple group defaults,dependent on which group the user has selected to turn on and theirindividual commands within the group default. During the set-up process,or any time after installation, a user can change the light default orgroup default settings through the device application.

The manufacturing default will most likely be a standard high outputwhite type of light. This light setting will be programmed into each IIDevice during the manufacturing process and stored into the II Device'smemory. This default will first be executed when the II Device ispowered on for the first time. As such, the manufacturing default isindependent of the device application. After a light default isassigned, the light default setting will take precedence over themanufacturing default, however the manufacturing default setting willstill stay stored within the II Device's memory. When a light is resetto the manufacturing state, either through the hard or soft resetfunction, the light default will be erased and the II Device will revertback to the manufacturing default acting as the light default.

Referring now to FIG. 34, a flow chart of a process for creating oradjusting a light default in accordance with one embodiment of thepresent invention is shown and referred to as 3400. The process beginsat block 3402. At any time after setting up an II Device with the deviceapplication such as the process described in 3900, a user can select oradjust a personalized light default setting. A user can select one ormore II Device(s) through the device application 3406, adjust the colorand/or brightness 3408 and set that selection as the light default forthe respective II Device(s) 3410. Upon assignment of the light default,the device application via the wireless device will send a wirelesscommunication to the related II Device(s) 3412, through an appropriatecommunication means. The communication will instruct each II Device tostore its respective configured setting in its internal memory as thelight default setting, instead of the manufacturing default orpreviously assigned light default 3414. This communication request willthen be executed by the controller and related components, including thestorage of the new light default in the II Device's memory 3416. Theassigned light default light setting will also be stored in the deviceapplication memory 3418. This would end the process for setting a new orchanging an existing light default setting 3420. The light defaultsetting can be changed or adjusted at any time and would follow asimilar, if not the same, process for creating a new light default asdescribed as element 3400. Each II Device can only have one lightdefault at a time.

Now referring to FIG. 35, a flow chart of a process for creating oradjust a group default in accordance with one embodiment of the presentinvention is shown and referred to as 3500. The process begins withblock 3502. First, the user would select the group to assign or adjust agroup default 3504. This could happen either through selection of anexisting group in the device application 3506 or when a user creates agroup as in the process 3200. A selected group might consist of onegroup or multiple groups together. The user will then need to specifythe particular light setting for that selected group(s) to execute whenturned on as a group 3508. Once a group default is selected for thegroup 3510, the associated light setting for each II Device within thegroup will be stored within the device application 3512, to be executedat that time or in the future. If a group default is set for associatedII Devices that do not have a light default 3514, the group defaultlight setting will also be assigned and communicated to each related IIDevice as the light default light setting 3516. This will most likelyhappen during the initial set-up and grouping process. In this scenario,the device application and related wireless device will execute thewireless command similar to that in setting a light default 3400, andthe group default process will be complete as signified by block 3520.Similarly, if unedited at the light default level, future changes to thegroup default will similarly change the respective light defaultsetting. When an II Device associated with the group already has anassigned light default 3514, but that light default was originally setby creating that same group default that is being configured 3518, thenthe light default will be adjusted as the group default it wasoriginated from is adjusted 3516 and each II Device will execute theprocess to adjust its default light setting with the group default lightsetting as in the process 3400. The group default process will then becomplete as signified by block 3520. If the light default setting didnot originate from the group default being configured 3518, then thelight default will not be updated and the group default process will becomplete as signified by block 3520. When the group default is executedit follows a similar process as that for executing a group command or3300. Once a group default is selected for the group, the associatedlight setting for each II Device within the group will be stored withinthe device application, to be executed at that time or in the future.When the group default is executed, the device application will recallall II Devices within the group and the associated saved light settings,then send a wireless command through the device application to allassociated II Devices within the group requesting those II Devices toexecute the saved light setting. The wireless communication would beextended and confirmed similar to the mesh network protocol. As a singleII Device might be related to multiple groups, is similarly would havemultiple group default settings. A group can be adjusted, changed, oradded at anytime by the user through the device application. Anytimeafter installation, a user can save or adjust the light default or groupdefault related to an individual II Device, multiple II Devices, asingle group, or multiple groups. Adjusting either the light or groupdefaults would follow the same process as setting a new default.

Referring now to FIG. 36, a flow chart of a power restoration process inaccordance with one embodiment of the present invention is shown andreferred to as process element 3600. The process begins with block 3602.Anytime an II Device goes from not having an electric current 3604 tohaving an electric current 3606, for any period of time, the II Devicewill execute the power restoration mode 3608. If a light default isassigned to the II Device 3610, the power restoration mode will triggerthe II Device to recall the light default setting from its internalmemory and execute the light default setting 3612. If unassigned 3610,the II Device will recall the manufacturing default setting from itsinternal memory and execute the manufacturing default setting 3614. Inaddition, the power restoration event and/or association in executingeither the light default setting or manufacturing default setting couldact as an input event or condition for specific programs 3616, such asthe quick set-up or quick grouping processes, or as a status definedevent 2101 or part of the II Device's next status update 3618 asdescribed in 2100 or 2200. The process ends with block 3620. This wouldcommonly occur when a light switch is changed from off to on, or from onto off to on. A user would not need to utilize the device application totrigger the light default action in this sense. The power restorationmode, or more simply turning the power source to the II Device off, willcease any currently running (the II Device is executing it at that time)program, scene, or setting, but will not erase any program that isactive (set to be run in the future) and its associated setting from theII Device's memory. Upon resetting the II Device, either through a hardreset or a soft reset, the light default will be erased. Powerrestoration mode will then revert to the manufacturing default lightsetting. A user could choose not to utilize the power restoration modecan by turning it off through the user's settings on the deviceapplication.

After setting up defaults, a user can simply turn on any combination ofII Devices and/or groups to their assigned default via the deviceapplication. Now referring to FIG. 37, a flow chart of a process forexecuting a default command through an on/off toggle in accordance withone embodiment of the present invention is shown and referred to as3700. The process begins with block 3702. A user would select thedesired II Devices and/or groups through the device application 3704 andtoggles the basic ‘on’ command related to executing the selection'srespective defaults 3706. When toggled ‘on’ the device application wouldretrieve the appropriate saved default including the related II Devicesand their associated light settings 3708. The wireless device would thensend an appropriate wireless communication to the II Device(s)/group(s)to execute their respective light setting 3710. Each related II Devicewould then receive and execute the command 3712, and then it willrespond to the wireless device confirming execution of the command 3714following the appropriate communication methods/processes. The processwould end with block 3716. A user could turn off or adjust any runningdefault command through the process outline above 3700.

Referring now to FIGS. 38A-F, diagrams of various scenes on deviceapplication in accordance with one embodiment of the present inventionare shown. The device application will generally be run on a wirelessdevice such as a smartphone, table, or computer. In these cases, thedevice application will most likely have the below screens and sectionsto support user control of the wireless lighting control system. A usercould toggle between screens through various human computer interactionmethods, dependent on the wireless device, but most commonly will begestures and/or touch selections.

As shown in FIG. 38A, a device 3800 displaying a favorites screen 3802will display a list of user generated favorite commands relating to IIDevices, groups, programs, and scenes. Each item displayed on thescreen, as exemplified by 3804 as one item, would be a specificselection of II Devices and an associated action that could be activatedthrough toggling of the on/off button, represented by 3806. Whenselected, the wireless device and related II Devices will execute therelated communication method for that command. A user can also add ordelete favorite settings through this screen or various other screens,for example a user could select 3808 in the figure to perform thiscommand.

As shown in FIG. 38B, a device 3800 displaying a groups screen 3818 willdisplay a list of all groups created within the device application'sprofile. Each or multiple groups, as exemplified by one group as 3820,could be selected to turn on to the group default setting, or off;exemplified by the selection of 3822. Each or multiple groups could alsobe selected and then given some specific command or other option asoutlined in the groups section. When selected, the wireless device andrelated II Devices in the group (s) will execute the relatedcommunication method for that command. A user can also select a group toview the individual II Device screen filtered to just that group. A usercan add, edit, and or delete group(s) and default group settings throughthis screen or various other screens, for example a user could select3824 in the figure to perform this command.

As shown in FIG. 38C, a device 3800 displaying a programs screen 3832will display a list of all programs created or suggested (manufacturingdefault programs) within the device application's profile with an on/offstatus for each program. Each program, as exemplified as one program by3834, could be selected to turn on or off, a command potentiallyexecuted by toggling 3836. Additionally, each program could be selected,edited, or deleted. When a program command is selected, the wirelessdevice and related II Devices to the program will execute the relatedcommunication method for that program. A user can add or deleteprogram(s) through this screen or various other screens, for example auser could select 3838 in the figure to perform this command.

As shown in FIG. 38D, a device 3800 displaying a scene screen 3848 willdisplay a list of all scenes created or suggested (manufacturing defaultscenes) within the device application's profile with an on/off statusfor each program. Each scene, as exemplified as one item by 3850, couldbe selected to turn on or off, a command potentially executed bytoggling 3852. Additionally, each scene could be selected, edited, ordeleted. When a scene command is selected, the wireless device andrelated II Devices to the scene will execute the related communicationmethod for that scene. A user can add or delete scene(s) through thisscreen or various other screens, for example a user could select 3854 inthe figure to perform this command.

As shown in FIG. 38E, a configure screen 3860 is used to adjust thecolor 3862, brightness 3868, saturation 3874, and other configurationfor selections of II Device(s), group(s), program(s), and/or scene(s).The configure screen 3860 might be different depending on the selectionand specific type of configuration. In general, the configuration screen3860 will consist of the three level lighting control interface 3850 anda list of the selection (II Device(s)/group(s))/etc.) 3852. There wouldmost likely be related configuration screens for the selection ofprogram conditions, scene creation/editing, and other more complexconfigurations.

As shown in FIG. 38F, a device 3800 displaying a II Device screen willdisplay a list of all II Devices either selected or identified withinthe device application's profile, the screen represented by 3882. EachII Device, as exemplified as one II Device by 3884, could be selected toturn on or off to the light default, a command potentially executed bytoggling 3886, or configured in some other fashion. Additionally, eachII Device or combination of II Devices could be selected, edited, orgiven some other command or selection as outline in the basic controlsection. When an II Device command is selected, the wireless device andrelated II Device(s) will execute the related communication method, forexample a user could select 3888 in the figure to perform these types ofcommands.

Referring back to FIG. 38E, certain II Devices with color and whitecould be controlled through three levels: color 3862, saturation 3868,and brightness 3874. This functionality is derived by the capabilitiesof the schemes in the LED controlling circuit and related LEDs andsupported device application. Color levels would be derived by combiningdifferent variations and combinations in the average luminosity passedthrough the II Device's LEDs. A color level selection 3862 refers to aninput on a user interface that would go to create any number of colorsderived from the mixing of the LEDs found in the II Device. The colorlevel could be controlled incrementally or at fixed points, for examplea user could select a color level from a color slider 3864.Alternatively, a user could select specific colors from the color levelsuch as blue, green, red, etc. as represented by 3866.

Brightness levels would be derived by either increasing or decreasingthe average current passed through the LEDs of the II Device, but in thesame proportion as that required for the selected color. The differencein brightness levels would only be apparent in variations in theluminosity of the light emitted from the II Device. The color will stayconstant when adjusting the brightness. Similarly, a brightness levelselection 3868 could be controlled incrementally or at fixed points, forexample a user could select a brightness level from a slider 3870.Alternatively, a user could select specific brightness levels such as25%, 50%, dim, bright, etc. as represented by 3872.

Saturation levels would be derived by adding or subtracting someproportional amount of average current passed through the white LEDswith respect to the average current combinations of the set color. Theoverall effect of increasing the saturation level would be reducing therelative amount of white light produced by the II Device in relation tothe colored LEDs. The overall effect of decreasing the saturation levelwould be increasing the relative amount of white light produced by theII Device in relation to the colored LEDs. Similarly, the saturationlevel selection 3874 could be controlled incrementally or at fixedpoints, for example a user could select a saturation level from a slider3876. Alternatively, a user could select specific saturation levels suchas 25%, 50%, lighter, darker, etc. as represented by 3878. Note that thechange in saturation selected through the device application would notnecessarily have a linear relationship to the amount of white lightadded or reduced, but it could be exponential or through some othercalculation. The overall effect and process would manage the saturationlevels so that the perceived difference is gradual to the user, whilemanaging for the constraint in the amount of current available to theLEDs. With the present invention, a user can utilize any number ofpreset lighting and automation programs or create his/her own. Forexample, the user can enjoy his/her breakfast in invigorating whitelight and later adjust the ambiance to a deep red light for a romanticdate.

Now referring to FIG. 39, a flow chart of a quick set-up process forconnected lights in accordance with one embodiment of the presentinvention is shown and referred to as 3900. A process that allows an IIDevice or multiple II Devices to quickly and securely establish aconnection with a wireless device and the associated device applicationand with other connected II Devices around it. Further, there are someunique processes with regard to the invention presented here in terms ofthe set-up of the light and application. In one embodiment, theapplication will have a set-up mode where a signal is sent out and alllights that are on return a signal that creates a quick grouping oflights. In another embodiment, in a set-up mode a signal is sent out toall bulbs in a network to discover new lights. The signal is received byall lights that have power and return a signal. Then the lights thathave not yet been assigned to the application step-through a blink, oneat a time, prompted the user to name and add the light to anypre-assigned group or create a new group. The process will continueuntil all new lights have been assigned. The process begins in block3902. Each II Device when initially purchased or reset will be in amanufacturing state 3904. This state will also be recallable when thesmart light is reset. When in a manufacturing state, upon receivinginitial power (current), the II Device(s) will enter power restorationmode 3906 as described in FIG. 36. The II Device(s) will then be proneto discovery by a wireless device with the associated device application3908. The II Device(s) would also execute the manufacturing defaultlight setting 3910. Upon launch of the quick set-up process on thedevice application 3912, the wireless device and II Device (s) in themanufacturing state will then identify and connect to each other ifwithin range or through an extended mesh network in the manufacturingstate to create a secure paired connection 3914. Through mesh network IIDevices would look for all other II Devices, regardless of whether theyare in manufacturing state or already associated to the deviceapplication and related profile. The II Devices will ignore anyconnection with a smart light associated to a different user profile.The device application on the wireless device will then store eachdetected II Device's unique ID 3916, so that it can communicate with itin the future. Each II Device would similarly recognize and store aunique ID associated to the user's device/profile 3918, so that onlythat smartphone/profile ID can send directions to the II Device in thefuture 3920. Similarly, the II Devices could send commands andcommunicate with each other.

In some embodiments—the set-up process could use different color lightsettings as cues in the set-up process. For example, the II Device woulddisplay a certain color upon initial power up, signaling to the userthat the II Device is not connected to the network. Then uponestablishing connection to a profile, the II Device would change colorsto signal the connection has been established 3922. Next, a user mightconfirm that all II Devices are connected and select an option in thedevice application to move forward with the set-up 3924. If not allconnected, then execute troubleshooting steps with user. Identifyproblem II Devices. Execute quick troubleshooting steps 3926—stepcloser, screw in/secure connection to power source. User can possiblyprovide confirmation through the device application that all II Devicesare a specific color. All II Devices become connected, and user selectsoption that II Devices are not all connected, then prompt to selectcolor of light. Should be color of unpaired light or no light, ifunpaired light, ask user to step closer to the II Device and select OK.Then should connect and user can continue set-up. If no light, ask userto make sure that the II Device is firmly screwed in and the lightswitch is on. Then proceed through set-up menu. Once user confirmsset-up of installed II Devices 3924, they can continue with any furtherset-up or customization processes 3928, such as adding names, defaults,and favorites. Once confirmed, a user will then be able to send acommand to any of the related II Devices. Similarly, the II Devicescould send commands and communicate with each other. A user can repeatthis process to continue setting up other II Devices 3930 until allintended II Devices are set-up and the quick set-up process is complete3932.

Referring now to FIG. 40, a flow chart of a quick group process throughpower restoration in accordance with one embodiment of the presentinvention is shown and referred to as process element 4000. A quickgroup process through power restoration provides a quick way for a userto combine II Devices into a named group through use of the powerrestoration mode. It could be a guided process within the set-up processof the II Device network through the device application as described inFIG. 39. It also could be run after the initial set-up of the II Devicenetwork. Further, there are some unique processes with regard to theinvention presented here in terms of the set-up of the light andapplication. In one embodiment, the application will have a set-up modewhere a signal is sent out and all lights that are on return a signalthat creates a quick grouping of lights. In another embodiment, in aset-up mode a signal is sent out to all bulbs in a network to discovernew lights. The signal is received by all lights that have power andreturn a signal. Then the lights that have not yet been assigned to theapplication step-through a blink, one at a time, prompted the user toname and add the light to any pre-assigned group or create a new group.The process will continue until all new lights have been assigned. Thisrelates to any number of II Devices and requires the device application.A user can select to go through a quick group process either during orafter the initial set-up of the smart light network. The quick groupprocess is a unique way to quickly navigate a user through creatingbasic ‘room’ based groups, through the device application. The processbegins with block 4002. Upon launch of the quick group process throughthe device application 4004, though device application instruction, orin the natural course of set-up, the user will turn off the power sourceto the related II Devices that they would like to group, then turn thepower source back on 4006. When done, this will prompt the related IIDevices to enter the power restoration mode 4008. This action will mostlikely be through the use of a wall switch. The II Devices will executethe appropriate default setting as discussed in FIG. 36. The deviceapplication and related wireless device will then search for all IIDevices that have entered the power restoration mode through variouscommunication methods previously discussed, record their unique IDs4010, and display the associated II Devices through the user interfaceon the device application or some other type of user feedback means4012. A mesh network can be used to extend the wireless signal. The userwill then be prompted to confirm that the correct II Devices werecaptured 4014 within the group through the device application. Could usecolor cues to help with the confirmation as discussed in FIG. 49. Ifuser does not confirm, then go to troubleshooting steps 4022. If yes,then continue with the process to create a new group 4016 as outlined inFIG. 32. The user will then be asked to assign a name for the groupthrough the device application following the rest of the standard groupcreation process. The user would then be asked to set a group defaultlight setting for the new group through the device application byexecuting the process for group default creation. After setting up aquick group the user might then be asked if they would like to set-upanother quick group through the device application 4018. If yes, thenrepeat the quick group process 4002. If no, then end quick group process4020.

Upon initial set-up of a lighting network, a user will create a profile.Profile refers to a combination of unique username and password thatwould be related to one or many user's accounts. The profile would havemultiple purposes—1) to provide an authentication method forcommunication within the wireless lighting system (network of II Devicesand wireless devices), 2) to associate and save user preferences andconfigured settings of the wireless lighting system to the deviceapplication and possibly saved elsewhere, and 3) provide a userassociated account for billing, support, or other services. Through theinitial set-up process, as described in FIG. 39, each II Device within alighting control system will store the Profile's username and passwordor some encrypted version of the profile's username/password in itsmemory. Similarly, the wireless device and device application will storeall II Device ID's within the lighting control system (lighting network)to the device application memory.

Now referring to FIG. 41, a flow chart of a profile authenticationprocess in accordance with one embodiment of the present invention isshown and referred to as 4100. See also FIGS. 22-26 for other relatedprocess information. The profile authentication process begins in block4102. Upon any communication (e.g., user selected command) from awireless device or other II Device to one or many II Devices, thewireless communication will include some version, possibly encrypted, ofthe associated profile 4104. Upon receipt of the wireless communication4106 by the targeted II Device(s), the II Device will verify orauthenticate the command by referring to the stored profile(s) in thecommunication. If the profile from the wireless communication, recoveredfrom the II Devices memory 4114, matches that of the stored profile(s)4108, then the II Device will execute the appropriate response specifiedby the wireless communication 4110. If not, then the II Device willdisregard the communication 4112. The process ends then at block 4114.Similarly, when a II Device receives a command or status update fromanother II Device, it will verify that the wireless communication refersto a profile that matches the stored profile(s) in its memory. If itmatches, then it will take some action described by the wirelesscommunication, and if not, then it will ignore that communication.

Referring now to FIG. 42, a flow chart of a process for saving settingsunder a profile in accordance with one embodiment of the presentinvention is shown and referred to as element 4200. The process beginsin block 4202. After a user has created a profile 4204, when a usercreates any number of settings or information as represented as 4206(programs, defaults, groups, scenes, favorites or other information),the settings and related information can be saved to the deviceapplication memory under the heading of the user's profile 4208. Thiswould allow for replication and/or back-up of user preferences to avoidloss of data and user convenience 4210. In addition, this would allowfor sharing, duplication, and restoration of user settings throughauthentication means by referring to the user profile 4212.

In some cases, a user could save their profile and associated settingsto a computer 4214, either through the back-up of the application toapplication management software (iTunes, etc.) or through some lightcontrol system specific back-up software. In addition, the profileinformation and settings could be saved or backed up through a directconnection or through some wireless connection. In addition, the profileinformation could be saved to a remote data center, or in ‘the cloud’4216, and saved and recalled upon command or some frequency. The timingand exact process of a profile saving event 4224 might differ dependingon the device application. It might happen automatically at given timeperiods or events, or require some input from the user to either specifyevents/times, or require a user to select a save option.

After a profile is saved or ‘backed-up’, it can be accessed throughlogging in to the device application with the associated profile'susername and password. In this sense, a user could restore settings andprofile information to an existing or new wireless device/deviceapplication 4218. A user could share the profile information andauthentication as described in FIG. 43 and included here as block 4220.A similar process would be used for adding a new wireless device withdevice application running the same profile or duplication 4222. Notethat there may be multiple profiles assigned to one lighting controlsystem or II Device network. Similarly, the same device applicationcould host multiple user profiles. The same profile could be sharedacross multiple wireless devices. Though the actual process might beongoing, for the purposes of this description, the process ends in block4226.

All II Device(s) will have unique id(s). Ids will depend upon the typesof II Device embodiments. There could be different types of II Devicesdepending upon the application where they will be used (e.g., II Devicesmade for higher light (luminosity) output and limited color range couldbe called as type 1 II Device, while II Device with only white lightoutput with controllable brightness could be called as type 2 IIDevice). Similarly, there would be different types of II Devices basedupon different shapes and/or sizes and/or features and/or light outputsin terms of colors and brightness. There could be numerous potential IDstructuring of the II Devices, but consider the below as arepresentative example.

II Device id will have following structure with “aaabbbccc”. “aaa” couldbe any number of characters defining the device as II Device. Thesecharacters will be common and at the same place in the ids of all IIDevices. “bbb” could be any number of characters defining the type of IIDevice. These characters will be common for a particular type of IIDevice, but will be different for different types of II Devices. Thesecharacters will at the same place in the id of all II Devices. “ccc”could be any number of characters and with that II Devices will get aunique id. For example, consider id “Smartlightt001001012712”,“Smartlightt012234010512” for two different II Devices—here, first tencharacters “II Device” in both the ids will identify the device as IIDevice. Next four characters “t001” in first id and “t012” in second ididentifies the devices as different types of II Devices. Last 9characters “001012712” in first id and “234010512” in second id combinedwith other characters defines a unique id for the two II Devices.

The wireless lighting control system, including both wireless devicesand II Devices will be able to differentiate its related commands fromother wireless communication system commands through the unique IDsprefix, such as “aaa”. Additionally, a wireless communication within thewireless lighting control system would also be associated with a profileid for authentication purposes. When a wireless device then sends acommand to an II Device it will send the command directed at thespecific II Device ID required to execute that command. Similarly, therecould be a command related to a specific II Device ID that is embeddedin a command sent to another II Device ID, in this case the secondcommand would communicate to send the command to the second II Device.See mesh network processes for further information.

Profile Sharing. A user's profile including their configured settingscan be transferred in a multitude of ways from an authenticated deviceapplication/wireless device to other non-authenticated deviceapplications/wireless devices to provide authentication, share profilesettings and information, or other profile related information.Additionally, the application settings, programs, customizations, andidentification groupings can be transmitted from device to devicethrough Bluetooth signal in the control application through a share mysettings mode. This will make it easy to pass on settings to new usersand allow for multiple controller devices being able to address the samenetwork of lights, from lease to lease or party to party. Utilizing thedevice application, there is an option to pass on authorization to thelighting control system (II Device network) from one wireless device toanother wireless device. Additionally, a user can share or copy theirprofile (saved settings) with another wireless device. The receivingwireless device would need to have some version of the deviceapplication on their device. There are a few different processes onecould take to execute profile sharing, but consider the below as anexample.

Now referring to FIG. 43, a block diagram of a device to device profilesharing process in accordance with one embodiment of the presentinvention is shown and referred to as 4300. To execute this process, onewould open the authenticated device application on one wireless deviceas represented by 4302. Then open the device application on thereceiving or new wireless device as represented by 4304. A user wouldthen select command on the authenticated wireless device application toshare profile. Might in some cases need to select command on thenon-authenticated wireless device to receive shared profile. Theauthenticated wireless device might then be prompted to select whataspect of the settings to share, such as provide access to network,share groupings, share programming, copy full profile settings, ormirror full profile settings. Upon selection of aspects to share, thewireless devices would then connect via a wireless communication 4306(Bluetooth most likely) and begin transferring the selected information,as represented by 4308, from the authenticated wireless device to thereceiving wireless device. Upon receiving the selected information theuser should have access to whatever aspects were selected.

Referring now to FIG. 44, a flow chart of a process for adding anauthenticated profile directly through the II Device in accordance withone embodiment of the present invention is shown and referred to as4400. In this process, the authenticated profile 4402 would send acommand or wireless communication to the wireless control system (IIDevice network), represented by 4404, with the command to add thenon-authenticated profile 4410 to each II Device's list of authenticatedprofiles. Each II Device, represented here collectively as 4406, wouldthen execute the command and add the authenticated profile to each IIDevice's list of authenticated profiles as represented collectively by4408. Once complete, the non-authenticated profile would then beauthenticated and able to communicate and control the lighting controlsystem (II Device network), as represented by 4412. Also, consider thata user could share/transfer a profile to one other device through text.An alternate way to share profile and settings would be to select anoption through the application to send a text message to another phone.This method would be useful when both devices are not present and thesecond device is a mobile device. The text message would include aunique URL to download the application and auto-populate the profileusername and possibly the password. In addition, consider that multipledevices could simply refer or log-in to an existing authenticatedprofile that has been saved to some accessible source. This would allowany wireless device with an associated device application to access,receive, or create and authenticate a new profile by logging in with theauthenticated profile's credentials (username password).

Now referring to FIG. 45, a flow chart of a hard reset process inaccordance with one embodiment of the present invention is shown. Theprocess begins with block 4502. A hard reset with physical button, andrestore to system will now be described. Included in the design of theII Device might be an external button that when pushed resets the IIDevice back to its original manufacturing state. This will be helpfulwhen moving II Devices from different locations or power sources, fortroubleshooting purposes, and for security purposes, especially when auser no longer has access to the application device. The physicaldescription and system composing the hard reset was previously describedabove. The process by which the hard reset occurs will be referred to as4500 and is described as follows, beginning with block 4502: (a) a userwill physically activate the reset button on the outside of an II Device4504; (b) a signal will then be sent to the internal processor of the IIDevice with commands to execute the hard reset program that will eraseall user added memory and return to the manufactured state 4506; (c) theprocessor and related components of the II Device will execute therequired commands of the hard reset program 4508; (d) all user addedmemory will be erased from the II Device, not including factory addedmemory 4510; (e) the II Device will return back to the manufacturingstate 4512. The process for set-up would continue with FIG. 48. The hardreset process ends with block 4514. Upon powering the II Device againafter the hard reset (entering power restoration mode), the II Devicewill then be ready to go through the quick set-up process. Once an IIDevice or II Devices are taken from an existing profile, reset, andadded back into the network of an existing profile, the user has a fewoptions. First, restore the II Devices with previous settings. Hereauthentication as well as all defaults, groups, programs,customizations, and naming conventions will be automatically restored toeach II Device previously reset. Each II Device's unique manufacturingID# will be matched to the application device's ID of the II Device,which will also have corresponding saved settings in the deviceapplication's memory related to the II Device's defaults, groups,programs, customizations, and naming conventions. Second, extend thesame settings from another II Device or group on the profile. This is asimilar process to introducing new II Device to an existing network.Third, create entirely new settings for the II Device. This is a similarprocess to quick set-up.

Referring now to FIG. 46, a flow chart of a soft reset throughapplication in accordance with one embodiment of the present inventionis shown and referred to as 4600. Included in the device application isan option that when selected will reset an II Device or multiple IIDevices back to their original manufacturing state. This will be helpfulwhen moving II Devices from different locations or power sources, fortroubleshooting purposes, and for security purposes. The soft resetprocess begins with block 4602. Within the application device, a userwould select a setting that activates the soft resets command andprogram 4604 to reset any number of II Devices on the system. Thissetting may or may not require authentication through entering of theusers profile and password 4606. When selected by the user, the deviceapplication would allow the user to select specific II Devices, groupsor the entire lighting system, with which to execute the soft resetfunction 4608. Depending on the user's selection, specific II Devices,groups or the entire system, the following events may occur. If specificII Devices are selected, the rooms menu will first appear and a userwill drill down into the II Devices menu for reach room to select anynumber of II Devices. The selection can span upon multiple groups and IIDevices. A user might use the ‘color coding’ process to selectindividual II Devices. The application might also display all II Devicessorted by group, location, or other factors, rather than have a userdrill down through the groups menu. If groups are selected, the roomsmenu will appear and a user can select any number of groups. If theentire system is selected, the application will select all II Deviceswithin the network and continue with the process. Upon selection, awireless communication will be sent from the wireless device/deviceapplication to each illuminated device selected, through the appropriatecommunication methods 4610. When each II Device receives thecommunication, the processor and related components will execute thesoft reset program and commands 4612, and all user added memory will beerased from the II Device 4614. Each II Device will return to themanufacturing state 4616. The process for set-up would continue withFIG. 48. The soft reset process ends with block 4618.

The process by which the soft reset occurs is as follows: (a) the userselects any number of II Devices or groups and confirms the resetfunction; (b) then a wireless communication will then be sent from thewireless device/device application to each II Device selected; (c) wheneach II Device receives the communication, it will be sent to theinternal processor of the II Device, and the communication will beinterpreted as a command to erase all user added data stored in memoryand return the II Device to the manufacturing state; (d) the processorand related components will execute the commands; and (e) upon poweringthe II Device again after the hard reset (entering power restorationmode), it will then be ready to go through the quick set-up process.Once an II Device or II Devices are taken from an existing profile,reset, and added back into the network of an existing profile, the userhas a few options. First, restore the II Devices with previous settings.Here authentication as well as all defaults, groups, programs,customizations, and naming conventions will be automatically restored toeach II Device previously reset. Each II Device's unique manufacturingID# will be matched to the application device's ID of the II Device,which will also have corresponding saved settings in the deviceapplication's memory related to the II Device's defaults, groups,programs, customizations, and naming conventions. Second, extend thesame settings from another II Device or group on the profile. This is asimilar process to introducing new II Device to an existing network.Third, create entirely new settings for the II Device. This is a similarprocess to quick set-up.

Now referring to FIG. 47, a flow chart of a process for adding a new IIDevice into an existing II Device network in accordance with oneembodiment of the present invention is shown and referred to as 4700.This is the process by which a user can easily introduce or re-introducean II Device or multiple II Devices that is (are) in the manufacturingstate into the II Device network. This process allows for a quick andeasy integration of new II Devices into a user's wireless lightingcontrol system, or reintegration of previously set-up II Devices backinto a user's wireless lighting control system.

Introducing a new II Device to an existing II Device network follows asimilar process as first setting up an II Device for the first time. Theprocess is similar to the quick set-up and easy room set-up processes.There are many potential processes to adding an II Device to an existingnetwork. Here is one example. The process begins with block 4702. Theintended II Device(s) will be in a manufacturing default, either comingfrom initial purchase or through a reset process 4704. A user willconnect the II Device(s) to a power source (most likely by screwing inand turning on a light switch) and open the application with the user'sassociated profile on a controlling device. Any II Device or number ofII Devices when initially purchased, or in the manufacturing state, willreceive power and enter the power restoration mode 4706. Upon receivingpower (power restoration mode), the II Device(s) will be prone todiscovery by the device application run on a wireless device and otherII Devices within proximity 4708. In addition, the II Device willexecute the manufacturing default light setting 4709. Then upon a userinput on the device application 4710 or through a standard status updateprocess where the new II Devices are found 4712, the device applicationwill execute the process for adding an II Device to the application4714. To elaborate, the status update process, as discussed in FIGS. 21and 22, might call for the device application to look for all II Devicespresent in proximity. This search will include identifying those IIDevices that are in a manufacturing state and prompted to be paired,and/or not yet assigned to a profile. Next, the device application andassociated wireless device establish a connection with the Device(s)4716. If the device application on the wireless device finds any IIDevice(s) that are in the manufacturing state, it will provide an optionfor the user to select or confirm whether they are adding other IIDevices to the II Device network 4718. If a user selects no, it willignore the II Device's request to pair and end the process of adding anew II Device to an existing network 4720. This might happen by rarechance when people in neighboring apartments or buildings install IIDevices at the same time within range from each other. If a user selectsyes to confirm the addition of new II Device(s), the light ID will bestored in the device application memory and the profile ID will bestored in the device application memory. A user might then be promptedwith other choices on how to add the II Device to the network, includingin a group, mirroring/assigning defaults, etc. Continued set-up wouldfollow traditional set-up of II Device(s) until complete, as describedin process outline in FIG. 39, blocks 3916-3926, collectivelyrepresented here by block 4722. This includes storing the light ID inthe device application memory and storing the profile ID in the deviceapplication memory. Then, in place of block 3938 to move forward withthe set-up process, a user might then be prompted with other choices onhow to set-up and customize the II Devices within the network 4724,including adding the selection to an existing group 4726, creating a newgroup with new or mirrored settings for the selection 4728, or creatingcustom settings for each II Device in the selection 4730. Depending onthe user's request, the appropriate set-up would continue as describedin other various set-up processes 4732, until complete 4720.

FIG. 47 is also representative of a flow chart of a process forreintegration of a II Device back into an existing II Device network inaccordance with one embodiment of the present invention. Consideringthat the adding of the II Device(s) has proceeded through until block4716, where the device application/wireless device and II Device(s) haveestablished a connection. If the device application finds that the IIDevice ID (or multiple IDs) matches that of an II Device ID stored inthe device application 4734, then it should trigger the II Devicereintegration sub-process. If there is no match, then the process ofadding II Device(s) would continue as normal along block 4718 asdescribed previously. After finding a match to a previous II Device, thedevice application might confirm that the user would like to reintegratethe detected II Device 4736. If the user selects no, then the process ofadding II Device(s) would continue as normal along block 4718. If theuser selects yes, then the device application would then reassign orreconnect all stored information, profiles, defaults, and other settingsto the associated II Device(s) ID as stored in the device applicationmemory collectively represented as block 4738. This would require thedevice application/wireless device to then send a command to the IIDevice(s) to execute/store the following: (a) all related profile IDs(if stored or connected to the active profile ID); (b) all profilesettings including light default(s), active programs, and time settings.The newly connected II Device upon receipt will execute/store thecommands and respond to confirm receipt. The device application willsimilarly update its memory with the re-inclusion of the II Device(s),and they will then be re-integrated into the II Device network with allpreviously stored settings in the device application, and the processwill end in block 4720.

Referring now to FIG. 48, another embodiment 4800 of II Device 140system with the wireless energy receiver 4804 and wireless energytransmitter 4802 is shown. The wireless energy transmitter 4802transmits the energy wirelessly to the II Device 140 through wirelessenergy receiver 4804. The wireless energy receiver 4804 that isconnected to II Device 140 feeds the energy received to the II Device140 through its connector 100 or directly to the AC/DC converter 102. Inthis case, the input ratings of AC/DC converter 102 might be differentthan the universal ratings as explained earlier (AC power 60 V-290V/45-65 Hz). Wireless energy receiver 4804 may have inbuilt AC/DCconverter in which case, the DC output generated of wireless energyreceiver 4804 is directly given to the DC/DC converter 104.

Now referring to FIG. 49, a block diagram of a color codingidentification process in accordance with one embodiment of the presentinvention is shown and referred to as 4900. It might be difficult for auser to select a specific II Device(s) for troubleshooting orconfiguration, especially as the number of II Devices within a networkincreases. To improve the process of selecting specific II Device(s),described herein is a method to temporarily change the color of IIDevices in the II Device network and similarly provide a display ofdifferent II Devices on the device application that mimic the samecolors of their representative II Devices. This process might beexecuted in relation to a number of different activities or processes.We'll assume for simplicity sake that any potential processes couldtrigger the process to color the II Devices and refer to such an eventas ‘color coding process trigger’.

Upon a color coding process trigger, the device application would assigna different color to each of any number of selected II Devices and/orgroups. The device application/wireless device would then send awireless communication to each of the selected II Devices to execute alight control setting relating to the assigned color for that II Device.The device application as represented by 4902, would then display all ofthe selected II Devices with a representation of the light that'semitted by that particular II Device each represented as 4904-4920. Auser would then be able to visually see which II Device relates to theII Device representations in the device application and easily selectthe intended II Device(s). For example, the II Device represented by4904 would be colored red in some fashion, and the actual correspondingII Device would emit the same red color.

Referring now to FIGS. 50-52, various diagrams of sorting screens basedon various criterions in accordance with one embodiment of the presentinvention are shown. For certain screens within the device application,it would be beneficial to sort the list of II Devices and/or groups insome fashion that would be relevant to the user. Disclosed herein aresome basic sorting methods with which to sort certain lists found withinscreens of the device application.

As shown in FIG. 50 and represented by 5000, it would often be the casethat a user would want to command or control II Devices in closerphysical proximity than those in further proximity to the user. Tosupport this scenario, certain lists 5006 in the device application 5002could be sorted by signal strength with stronger signals displayed firstin the device application, represented as example by 5004. This couldrelate to lists of: (a) II Devices—sorted based on individual signalstrength; (b) Groups—sorted based on average signal strength of relatedII Devices; (c) Programs/scenes—sorted based on average signal strengthof related II Devices. The figure represents a list of groups sorted bysignal strength, with each group and its associated signal strengthrepresented by 5008-5016.

As shown in FIG. 51 and represented by 5100, it would often be the casethat a user would want to command or control II Devices that arecurrently executing some command. To support this scenario, certainlists 5106 in the device application 5102 could be sorted by theiractive status with items that are on displayed first, represented asexample by 5104. This could relate to lists of: (a) II Devices—IIDevices that are on displayed first; (b) Groups—Groups that are ondisplayed first; (c) Programs/scenes—Programs/scenes that are activedisplayed first. The figure represents a list of groups sorted by activestatus, with each group and its associated signal strength representedby 5108 —5116.

As shown in FIG. 52 and represented by 5200, considering that at timesall II Devices might not be available because their power source isturned off (light switch) or they are out of range, it might bebeneficial to sort/filter certain lists of items 5206 in the deviceapplication 5202 based on received statuses so that only those IIDevices for which statuses are received by the wireless device aredisplayed or displayed first, represented as example by 5204. This wouldrelate mostly to II Devices and groups, but possibly to programs andscenes where the un-addressable II Devices number is large. The figurerepresents a list of groups sorted by addressable status, with eachgroup and its associated signal strength represented by 5208-5216.

It would often be the case that a user would want to sort or filteritems in the device application based on some personal preferences orsettings. This might be flexible and configurable, or permanent,depending on the application. Note that different sorting methods couldbe combined in different ways, so as to first sort by one method andthen another. This would vary depending on the specific screen in thedevice application.

Now referring to FIG. 53, a flow chart of an automation programmingprocess in accordance with one embodiment of the present invention isshown and referred to as 5300. Automation refers to the program to beactivated at user specified conditions pertaining to day(s) of the week,times, and/or dates. Additionally, the solution provided by the presentinvention is more than energy efficient, providing the ability toautomatically turn on or off your lighting at specified times or to keeponly one bulb lit instead of an entire grid. The process begins withblock 5302. A user will select an option in the device application tocreate a program, specifically here an automation program 5304. The userwill select any combination and number of II Device(s) or group(s) 5306.The user will then select the intended light setting or program to beexecuted based on the automation condition 5308. This might originatefrom new user customization 5310, existing saved user favorites anddefaults 5312, or as a suggested setting or program 5314. The intendedlight setting might be a single action or more of a program in itself asmultiple actions run successively. For example, a simple automationprogram would turn the II Device(s) on to a specific setting and colorat a defined time. Alternately, another automation program would be toturn II Device(s) on and off successively. The user will then select aspecific day(s) of the week, date, and/or time to execute the settingand/or program 5316. The request could be a single event or repeatingevent selected by the user. For example, start on date/time, stop ondate/time. Or, run every third Monday of the month, etc. A user wouldhave the option to save the automation program 5318 and/or execute theautomation program at that time 5320. A user selects the II Device(s)and automation command to be performed, considering this the automationprogram. If the user saves the automation program, it can be re-run atanother time by following the process described in FIG. 29. Theautomation command is sent wirelessly to each of the selected IIDevices. The II Device(s) upon receiving the communication willinterpret and store the requested automation command in memory withinformation on when to execute the program. When the current date/timeheld in the real-time clock in each smart light matches that for theautomation command stored in memory, each smart light will execute theautomation program. If the user chooses to execute the newly createdautomation program, the device application/wireless device incoordination with the respective II Devices will execute the command asdescribed in FIG. 29 as if the program was activated as beginning withblock 2908. After both cases the creation process would conclude asrepresented by 5322. Upon completion of the automation program and suchthat no future conditions exist in the automation command at anothertime, the II Device(s) will erase the automation program and relatedautomation command from the II Device's internal memory.

Similar to all programs, the user can toggle automation programs on/offvia the device application. When the program is off, the II Device(s)will not store the command in memory. When the automation program istoggled on in the future, the command will be resent to the appropriateII Devices. In the case that conflicting programs are active with theuser requested II Device(s) and time, the device application mightnotify the user and ask for the user to select which program they wouldlike to keep active. Alternately, the II Device(s) will internally havea priority level assigned to different profiles and/or types ofrequests.

An alarm_timer relates to a program process by which at a certain userdesignated time or lapse of time, an action would occur in any number ofII Devices or group of II Devices. The alarm_timer processes are similarto those described for general programs and automation programs. Throughthe device application a user would select the program to run the alarmor timer and select the II Devices and/or groups to execute the program.An alarm selection signifies that at a certain selected time, theselected II Devices and/or groups would execute an alarm command toadjust lighting to the user's requested command. The requested commandmight be of a dynamic nature or a program in itself so as an executionof multiple commands in sequence such as a flashing or changing of coloror brightness. When an alarm program is selected, the device applicationwould interpret the time requested by the user and send a command to thelights and/or groups selected to execute the command or series ofcommands at that specified time. Each II Device would receive thecommands through the wireless communication, interpret the commands bythe processor, and then store the request in memory to be executed at alater time. Inside each II Device, the processor would monitor theinternal real time clock and look for a match in the clock's time to thealarm program request stored in memory. If it matches, then theprocessor would execute the alarm command(s).

A timer selection signifies that after a certain amount of time passes,an II Device or combination of II Devices would act in some predefinedmanner. The user would first select the II Device, II Devices(s) and/orgroups, or multiple groups to run the program. Then the user selects theamount of time in minutes, hrs. etc. via their application. Onceselected then the device running the application will send a wirelesssignal to the designated II Device(s) with the specific amount of timeto count down from. At the point when all the II Device(s) confirmreceipt of the timer request to the device's application, the timer willbegin in unison with all II Device(s) applicable. Each II Device willthen countdown using internal real time clock, processor, and otherembedded components. If multiple II Devices, they will count downindividually, but all in unison. When the timer reaches zero, the IIDevice(s) will execute the command requested by the user. A user canrequest to repeat any timer programs to count down and then repeat. Theapplication interface might also present a timer display showing theamount of time counting down. Upon reaching zero, the application mightalso present some other actions within the application. This time downfeature might also be valued for gaming scenarios using the II Devicesas signals.

Referring now to FIG. 54, a flow chart of a music sync process inaccordance with one embodiment of the present invention is shown andreferred to as 5400. This is a type of program specifically forautomatically synchronizing the II Device(s) to music played on the sameenabled device. The device application will execute a specialapplication allowing for music played on the device to be interpretedinto commands given to any number of II Device(s). When launching theMusic Sync application, the application would look for addressablelights, additional lights addressed through the mesh network and howthey are addressable, and each lights status (Similar to launching theapplication). The process begins with block 5402. Through the deviceapplication or through a specialty device application, the user willaccess the music sync program 5404. The user would then select musicfile(s) stored on the device (or streaming music) to be played. The userwould then select the II Device(s) with which to sync the music 5406.The user would be presented with a list of their rooms (groups), or theuser could drill down to select individual bulbs or alternate bulbs. Theuser will then select the type of II Device arrangement and the lightsetting theme 5408. Options for selection could depend on a number ofdifferent factors, such as the number of II Devices selected 5410, theproximity of the selected II Devices 5412, suggested options 5414, userhistory or saved preferences 5416, or completely new customizedconfigurations 5418. For example, depending on the number of lightsselected, the device application will provide the user with a suggestedmusic sync setting. If the number of II Devices is 1, then the deviceapplication will only sync to a mono type interpretation of the audio.If number of II Devices is 2 or more, then the device application willevenly distribute and assign each II Device to either of the 2 primary(L, R) stereo channels within the music file. The device applicationwill visibly show each II Device and to which channel (L, R) the IIDevice are assigned to. The user will be able to move and reassignlights to different channels as well as select between mono or stereolighting modes. Hypothetically, if a music file is able to carrymultiple channels or if the music file can be broken into multiplechannels based on frequency, pitch, or other aspects of sound, a smartlight could similarly be assigned or distributed across multiple IIDevices.

Further considering arrangement, if a music file is able to carrymultiple channels or if the music file can be broken into multiplechannels based on frequency, pitch, or other aspects of sound, an IIDevice could similarly be assigned or distributed across multiple IIDevices. Similarly, considering selection of the light theme, the deviceapplication will display potential lighting themes options for the userto select or the user can customize their own preferences. Here, theremight be default settings that have a color and/or brightness themeassociated with each channel. The settings will be variations of coloror themes of color assigned to each channel. For example, one mightinclude all colors available randomly assigned to each II Device.Another option might allow for the channel colors to change over time.Another option might suggest only red hued colors, or any other type ofcolor hue. Once an arrangement and lighting theme is selected, the userwill be able to see and verify the selection 5420. At any time, the userwill be able to reconfigure the arrangement or light themes, 5422, suchas to move or reassign lights to different channels, select between monoor stereo lighting modes, or choose a different theme. Once theconfiguration is selected, the application device will notify theselected II Devices of the command and ensure all II Devices are readyand addressable 5424. This will be done via the appropriatecommunication and control processes. The user would then select musicfile(s) stored on the device (or streaming music) to be played 5426. Asthe music is played through the device application, the deviceapplication will interpret the music file wavelengths to send continuingcommands to each II Device previously selected to turn on and off,adjust brightness, and change colors depending on the music constructwithin that channel at that time and the selected arrangement and theme5427. There are multiple ways that the music output could beinterpreted, and only a few non-limiting possibilities will be describedherein.

Possibilities for interpreting the music construct is as follows: Foreach music channel in the music file (L,R), when there some output ofsound to be played or amplitude in the music, that would correlate withthe light(s) assigned to that channel to turn on (to emit light). Forexample, if a bass drum is played in the left channel, the audible soundwould coordinate to the visible light from that assigned left channel'sII Device(s). For each channel (as previously assigned), the brightnessof the light emitted by each II Device could brighten or dim dependenton the respective increase or decrease in amplitude of the music withinthat channels music file. Such as that louder sounds would coordinatewith brighter lights and vice-versa. Respective amplitude would be thedependent variable, not true amplitude. Additionally, different pitchranges might correlate with different color combinations of lightoutput. Additionally, the bpm (beats per minute) might be interpreted sothat after a standard measure of bars (time of playing) the color orchannel assignment of the II Devices might change.

A user could also adjust the overall brightness maximum output to theirpreference through the device application, similarly referred to in thefigure as 5422. This information would be taken into context beforerelaying commands through to the II Devices. The application devicewould automatically or through user input manage and match the output ofaudio to the output of lighting commands and delay the audio output toany delay in communication to the II Devices so as the actual soundheard through a speaker would match the same time that the lightilluminated from the II Device(s) 5428. They might have an option forthe user to calibrate the delay. The application would continue to runon the device while continuing to interpret/translate the music andchannels played into commands to be executed by the assigned IIDevice(s). When the music sync program application is stopped or exited5430, the assigned II Devices would revert back to their previousprogrammed state if applicable or default level 5432. The music syncprogram/application would complete 5434.

A predefined program so a user can set their II Devices to slowly turnon with certain color displays at specific times to simulate the effectof a sunrise. In many parts of the world, people have to get up beforethe sun, this process allows for a user to select their II Devices toturn on slowly, mimicking a sunrise, before their alarm or at a certaintime to help wake them up. Setting up the program through the deviceapplication, a user could select the special program through thepredefined program list or through the groups menu. The sunrise programwould be a suggested program for those groups containing the word‘bedroom’. The sunrise program could have a predefined length of 20minutes and would generally be paired with an alarm program. The userwould be able to adjust the length and type of sunrise if they choose.Type relates to variations in color schemes. The user will be asked toenter a time for the sunrise program to execute, or to create an alarmwith the sunrise. If the alarm program is also set, the two could be runsimultaneously or within one program. Once set and accepted, theapplication device will communicate the automation program request tothe selected light(s). The light(s) will receive the automation programrequest and store the program in memory to be executed upon therequested time. The program settings could be saved for future use orset to run at any frequency similar to any automation program.

Executing the program. When the sunrise program is active, the programwill be executed similar to any other automation or alarm program. Thesuggested colors used in the sunrise program will most likely includeorange and red colors that would brighten over time until fully lit whenthe alarm or timer condition is met. Blue LEDs might also be included toprovide the short wavelength light mimicking that of the sun.

In some embodiments, a light will be connected or equipped with anambient light sensor that can detect the light levels present within anarea, relay that information to the II Device's controller, which couldbe interpreted as a program input resulting in a change in the lightingbrightness and/or color. Even more-so, the present invention can be setto maintain a constant level of overall light in a room, regardless ofambient light. This SteadyBright feature is akin to cruise control forlighting, so that if it's brighter outside, your Bulbs can be set toautomatically dim to a preferred level. Dimming a light has been shownto save upwards of 30% of energy usage. Various programs are possible toutilize the II Device sensor's information as an input to causing someoutput in terms of a change in the brightness and/or color of one ormore II Devices. In one program example, a user will select a preferredlight level for II Device, II Device(s), group or group(s) through thedevice application. Each II Device can have a different setting, givingthe user to select any number of unique combinations. Selecting thepreferred level might also be done through the user defined defaults foreach II Device. When selected, the device application will then send arequest through the controlling device to each II Device that the userhas selected through the program, asking for each II Device's relatedambient light sensor information. The device application upon receivingthe light sensor information will store the default settings in theapplication or device's memory relative to each II Device.Alternatively, the II Device itself will record the sensor informationin its own memory. The user can then at any other time activate anautomatic adjustment program. Upon activation, the device applicationwill send a communication to each II Device associated with the program.The communication will instruct each II Device to compare the current IIDevice sensor information against that associated with the preferredlighting level. This information would either stored in the II Device'smemory or relayed via the device application's communication.

The II Device would then adjust its brightness and/or color depending onthe light sensor data's relationship between the current and preferredlighting level. Simplified, if the current light sensor showed lessluminosity than the preferred level, then the II Device would increaseits own brightness. Alternately, if the current light sensor showed moreluminosity than the preferred level, then the II Device would decreaseits own brightness. The relationship between the difference in currentand preferred light received will not be an equal or absoluterelationship to the change in the brightness of the light.Alternatively, it will be some functional relationship dependent on theabsolute and respective levels of light. The program and/or II Devicesthemselves would repeat this process for the duration that the programis active.

From the foregoing it will be seen that this invention is well adaptedto attain all of the ends and objectives hereinabove set forth, togetherwith other advantages which are inherent to the apparatus.

It will be understood that certain features and subcombinations are ofutility and may be employed without reference to other features andsubcombinations. This is contemplated by and is within the scope of theclaims.

As many possible embodiments may be made of the invention withoutdeparting from the scope thereof, it is to be understood that all matterherein set forth or shown in the figures of the accompanying drawings isto be interpreted as illustrative and not in a limiting sense.

It will be understood by those of skill in the art that information andsignals may be represented using any of a variety of differenttechnologies and techniques (e.g., data, instructions, commands,information, signals, bits, symbols, and chips may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof). Likewise, thevarious illustrative logical blocks, modules, circuits, and algorithmsteps described herein may be implemented as electronic hardware,computer software, or combinations of both, depending on the applicationand functionality. Moreover, the various logical blocks, modules, andcircuits described herein may be implemented or performed with a generalpurpose processor (e.g., microprocessor, conventional processor,controller, microcontroller, state machine or combination of computingdevices), a digital signal processor (“DSP”), an application specificintegrated circuit (“ASIC”), a field programmable gate array (“FPGA”) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. Similarly, steps of a method orprocess described herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Althoughpreferred embodiments of the present invention have been described indetail, it will be understood by those skilled in the art that variousmodifications can be made therein without departing from the spirit andscope of the invention as set forth in the appended claims.

What is claimed is:
 1. A lighting device comprising: an AC/DC or DC/DCpower converter; a controller/processor electrically connected to theAC/DC or DC/DC power converter; a light emitting diode (LED) currentcontrol circuit communicably coupled to the controller/processor andelectrically connected to the AC/DC or DC/DC power converter; two ormore LEDs comprising at least a first color LED and a second color LEDelectrically connected to the LED current control circuit; wherein theLED current control circuit provides an on/off signal having a cycletime to each LED in response to one or more control signals receivedfrom the controller/processor such that the two or more LEDs produce ablended light having a specified color based on how long each LED isturned ON and/or OFF during the cycle time; a wireless transceivercircuit communicably coupled to the controller/processor; an antennacommunicably coupled to the wireless transceiver circuit; wherein thecontroller/processor communicates with one or more other lightingdevices, remote controllers, sensors, other devices, or a combinationthereof; wherein the lighting device and the other lighting devices arepart of a mesh network, a group or a combination thereof; and whereinthe controller/processor provides a status information from the otherlighting devices, remote controllers or other devices within the meshnetwork or group.
 2. The lighting device as recited in claim 1, whereinthe specified color is produced by turning ON the first color LED for afirst portion of the cycle time and turning ON the second color LED fora second portion of the cycle time.
 3. The lighting device as recited inclaim 1, wherein the two or more LEDs are not turned ON at the sametime.
 4. The lighting device as recited in claim 1, wherein each on/offsignal provides a maximum current supplied by the AC/DC or DC/DC powerconverter to the LED.
 5. The lighting device as recited in claim 1,wherein the on/off signal for the first LED comprises two or more pulsesduring a portion of the cycle time that the first LED is turned ON. 6.The lighting device as recited in claim 1, wherein the on/off signals tothe two or more LEDs further produce the blended light having aspecified saturation.
 7. The lighting device as recited in claim 1,wherein the on/off signals to the two or more LEDs further produce theblended light having specified brightness or intensity.
 8. The lightingdevice as recited in claim 7, wherein the specified brightness orintensity is determined by a duty cycle of the on/off signals.
 9. Thelighting device as recited in claim 1, wherein the cycle time is lessthan 12 ms.
 10. The lighting device as recited in claim 1, wherein atleast one of the LEDs comprises a series of LEDs, a group of LEDs, anarray of LEDs, two or more series-connected LEDs, two or moreparallel-connected LEDs or a combination thereof.
 11. The lightingdevice as recited in claim 1, wherein the first color LED and the secondcolor LED are selected from the group consisting essentially of a redLED, a green LED, a blue LED, a red LED, a white LED and a tri-colorLED.
 12. The lighting device as recited in claim 1, further comprising areal time clock circuit communicably coupled to thecontroller/processor.
 13. The lighting device as recited in claim 1,further comprising a memory communicably coupled to thecontroller/processor.
 14. The lighting device as recited in claim 13,wherein the memory is integrated into the controller/processor.
 15. Thelighting device as recited in claim 1, further comprising: a powersupply connector/fastener electrically connected to the AC/DC or DC/DCpower converter.
 16. The lighting device as recited in claim 1, whereinthe LED current control circuit comprises a PWM driver, a switching ormultiplexer circuit, or one or more LED driver circuit.
 17. The lightingdevice as recited in claim 1, further comprising an ambient light sensorcircuit communicably coupled to the controller/processor.
 18. Thelighting device as recited in claim 17, wherein the ambient light sensordetects a level of one or more color components of an ambient light,wherein the one or more color components comprise a red, a green, ablue, a cyan, a yellow, a magenta, or a black.
 19. The lighting deviceas recited in claim 17, wherein the ambient light sensor is located todetect an ambient light and a light emitted by the lighting device suchthat the controller/processor adjusts one or more of the on/off signalsprovided to the two or more LEDs.
 20. The lighting device as recited inclaim 1, further comprising a hard reset circuit communicably coupled tothe controller/processor.
 21. The lighting device as recited in claim 1,further comprising an AC or DC power supply connected to the powersupply connector.
 22. The lighting device as recited in claim 1, whereinthe controller/processor receives a status information from the otherlighting devices, remote controllers or other devices within the meshnetwork and uses the status information as an input to execute one ormore commands, change the on/off signals, trigger a communication orcommand to the mesh network or group, or a combination thereof.
 23. Thelighting device as recited in claim 22, wherein the controller/processorenters a discovery mode to detect the other lighting devices within themesh network or group when the lighting device is turned on.
 24. Thelighting device as recited in claim 1, wherein the controller/processorexecutes one or more programs to control the LED current control circuitto produce a light in accordance with the one or more programs.
 25. Thelighting device as recited in claim 24, wherein the one or more programscomprise one or more default programs, one or more user createdprograms, or a combination thereof.
 26. The lighting device as recitedin claim 1, further comprising: a flexible strip; an electricalconnector affixed to the flexible strip; wherein the two or more LEDsare affixed to the flexible strip and electrically connected to theelectrical connector; and wherein the AC/DC or DC/DC power converter,the controller/processor and the LED current control circuit areremotely located with respect to the flexible strip and electricallyconnected to the electrical connector via a wire, a cable or aconnecting strip.
 27. The lighting device as recited in claim 1, furthercomprising a housing wherein the AC/DC or DC/DC power converter, thecontroller/processor and the LED current control circuit are disposedwithin the housing, and the two or more LEDs are proximate to or withinan aperture of the housing.
 28. The lighting device as recited in claim27, further comprising a heat sink disposed within or outside thehousing.
 29. The lighting device as recited in claim 27, furthercomprising a reflector disposed within the aperture of the housing andaround the two or more LEDs.
 30. The lighting device as recited in claim27, further comprising a diffuser or lens sealing the aperture of thehousing.
 31. A lighting system comprising: two or lighting devices,wherein each lighting device comprises: an AC/DC or DC/DC powerconverter, a controller/processor electrically connected to the AC/DC orDC/DC power converter, a light emitting diode (LED) current controlcircuit communicably coupled to the controller/processor andelectrically connected to the AC/DC or DC/DC power converter, two ormore LEDs comprising at least a first color LED and a second color LEDelectrically connected to the LED current control circuit, a wirelesstransceiver circuit communicably coupled to the controller/processor, anantenna communicably coupled to the wireless transceiver circuit, andwherein the LED current control circuit provides an on/off signal havinga cycle time to each LED in response to one or more control signalsreceived from the controller/processor such that the two or more LEDsproduce a blended light having a specified color based on how long eachLED is turned ON and/or OFF during the cycle time; wherein thecontroller/processors of the two or more lighting devices communicatewith one another using the wireless transceivers and antennas of the twoor more lighting devices; wherein the two or more lighting devices arepart of a mesh network, a group or a combination thereof; and whereineach controller/processor of the two or more lighting devices provides astatus information to the other controller/processors within the meshnetwork or group.
 32. A method for controlling two or more lightingdevices comprising the steps of: providing the two or lighting devices,wherein each lighting device comprises: an AC/DC or DC/DC powerconverter, a controller/processor electrically connected to the AC/DC orDC/DC power converter, a light emitting diode (LED) current controlcircuit communicably coupled to the controller/processor andelectrically connected to the AC/DC or DC/DC power converter, two ormore LEDs comprising at least a first color LED and a second color LEDelectrically connected to the LED current control circuit, a wirelesstransceiver circuit communicably coupled to the controller/processor, anantenna communicably coupled to the wireless transceiver circuit,wherein the controller/processor communicates with one or more otherlighting devices, remote controllers, sensors, other devices, or acombination thereof, and wherein the lighting device and the otherlighting devices are part of a mesh network, a group or a combinationthereof; sending one or more control signals from thecontroller/processor to the LED current control circuit corresponding toa blended light having a specified color; sending an on/off signalhaving a cycle time from the LED current control circuit to each LED inresponse to the one or more control signals such that the two or moreLEDs produce the blended light having the specified color based on howlong each LED is turned ON and/or OFF during the cycle time; a wirelesscontroller that communicates with the controller/processors of the twoor more lighting devices using the wireless transceivers and antennas ofthe one or more lighting devices; forming a mesh network, a group or acombination thereof using the at least two lighting devices; andproviding a status information from each controller/processor of the twoor more lighting devices to the other controller/processors within themesh network or group.